gap-analysis
/gap-analysis
Sprawdza wdrożenie względem kryteriów akceptacji i wypisuje każdą lukę, a także recenzuje cudzy pull request wraz z ticketem.
- Autor
- richardochristjia ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Sprawdza wdrożenie względem kryteriów akceptacji i wypisuje każdą lukę, a także recenzuje cudzy pull request wraz z ticketem.
Argumenty
/gap-analysis <.plans/task or slug> | <PR link> <ticket key>
Oryginalny opis (EN)
Checks an implementation against its acceptance criteria and lists every gap. Takes either a plan folder (.plans/{task}) to check the user's own work, including Record updates, or a PR link plus a Jira ticket key to review a teammate's PR in plain language, with a verdict and review comments ready to post. Use after a task loop finishes, for the autopilot's spec check, or when the user shares a PR and a ticket to review.
Jak działa
- Get both sides
- Acceptance-criteria table
- Plan mode
- PR mode
Podgląd SKILL.md
---
name: gap-analysis
description: Checks an implementation against its acceptance criteria and lists every gap. Takes either a plan folder (.plans/{task}) to check the user's own work, including Record updates, or a PR link plus a Jira ticket key to review a teammate's PR in plain language, with a verdict and review comments ready to post. Use after a task loop finishes, for the autopilot's spec check, or when the user shares a PR and a ticket to review.
argument-hint: "<.plans/task or slug> | <PR link> <ticket key>"
---
# Gap analysis
Compare what was built with what was asked. The arguments pick the mode:
- **A plan folder** (`.plans/<task>/` or its slug) → **Plan mode**: check the work against `plan.md`.
- **A PR link and a ticket key** → **PR mode**: review a teammate's PR against the ticket.
If the arguments don't make it clear, work it out from what's there: a `.plans/` folder on this branch means plan mode.
## Get both sides
- **What was asked:**
- Plan mode: `plan.md` (acceptance criteria, phases, Record Updates) and `tasks.md`.
- PR mode: run the read-ticket skill on the ticket key if you have it, else read the ticket with your issue tracker's tools, every custom field included. Custom fields are where acceptance criteria usually live. If it stops on blocking assets, stop with it.
- **What was built:**
- Plan mode: the branch's diff against the main line (`git diff <main>...HEAD`).
- PR mode: the PR's description, diff and review comments, through the GitHub CLI (`gh pr view <link> --comments`, `gh pr diff <link>`).
Read the code the diff touches until you can say, for each criterion, what the code does now. Never judge a criterion from a file name or the PR description.
## Acceptance-criteria table
| ID | Criterion | Met? | Evidence |
|---|---|---|---|
| AC1 | … | Yes / Partly / No / Can't tell | `file:line`, test name, or command output |
- One row per acceptance criterion: AC1, AC2, …
- Then one row per feature the plan, ticket or discussion expected that the criteria don't list: F1, F2, …
- "Can't tell" is an honest answer; a guess is not. Say what would settle it.
## Plan mode
After the table, reconcile the Record if the plan had Record Updates. Read `.agents/RECORD.md` if it exists. The implementer writes Record updates at the end of implementation, so they should be there by now.
- For each entry the plan promised, confirm it was written and matches what was actually built. A missing or mismatched entry is a gap.
- If the implementer reported a **divergence** (built differently, so it wrote no entry), check the divergence is real, then propose a correct entry, verbatim, for the user to approve.
- Any existing entry the work changed, broke, or made stale that the plan didn't cover is a gap. Propose the amended (or removed) entry verbatim.
- If the work established a new high-level fact with no entry yet, propose one in the Record's format.
- Skip cosmetic or unrelated edits.
End with:
- **Gaps:** one line each: its ID, briefly why it exists, and the fix.
- **Next:** a short list of what to do.
Report the gaps and stop; whoever ran you fixes them.
## PR mode
The user hasn't read the code or the acceptance criteria. Write so they can decide without opening either.
1. **Before and after:** what the product did before this PR and what it does now, in plain words, from a user's point of view.
2. **The acceptance-criteria table.**
3. **Verdict:** approve, request changes, or comment, with the one reason that decides it.
4. **Review comments, ready to post:** one per issue, each with its `file:line`, written to the PR author: friendly, specific, and with the fix. Say whether to post them as one review (request changes or approve) or as separate comments.
Never post on GitHub yourself unless the user asks.
Pliki w paczce (2)
- SKILL.md 4 KB
- agents/openai.yaml 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · richardochristjia/skills | 100 | MIT |
| anassahel/agent-labs | 100 | MIT |
| magnus919/agent-skills | 100 | MIT |
| kael-odin/codex-plugins-zh | 100 | MIT |
| afonsoft/skills | 100 | MIT |
| adeerkhan/vitruvius | 100 | MIT |
| qa-aman/claude-skills | 100 | MIT |
| testdouble/han | 100 | MIT |
| adrien-barret/claude-kit | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 6a7dcc967536 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 90mr-review
Przegląda merge request względem zgłoszenia w Jira lub Linear: sprawdza kryteria akceptacji, testy, bezpieczeństwo i wydajność oraz zapisuje uwagi po poleceniu. - 100implement
Implementuje wycinek, specyfikację lub ticket według kryteriów akceptacji, testem najpierw, a potem sprawdza wynik, upraszcza go i recenzuje. - 100verify-acceptance-criteria
Weryfikuje implementację względem kryteriów akceptacji w trakcie rozwoju funkcji, a nie przy zarządzaniu zgłoszeniami. - 100sl-ds-ticket-to-plan
Zamienia zgłoszenie z GitHuba w propozycję kryteriów akceptacji i plan wdrożenia zmapowany na pliki repozytorium. - 90implement-task
Realizuje uzgodnione zadanie z planu Markdown, Issue na GitHubie lub ticketu Jira i sprawdza kryteria akceptacji. - 90ticket-qa
Przeprowadza QA zgłoszenia z Jira lub Linear: zamienia kryteria akceptacji w plan zaliczeń, uruchamia testy lokalne i zapisuje dowody.