Przejdź do treści
Biblioteka skilli
Programowanie · Przegląd i audyt

plan-verify

/plan-verify

Weryfikuje niezależnie plan względem wzorców z bazy kodu, zanim rozpocznie się budowa.

Repozytorium
ship ↗
Licencja
MIT
Ostatnia zmiana repozytorium
25.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Weryfikuje niezależnie plan względem wzorców z bazy kodu, zanim rozpocznie się budowa.

Argumenty

/plan-verify [feature-name]
Oryginalny opis (EN)

Use when a plan has been created and needs independent verification against codebase patterns before building

Jak działa

  1. Find Active Feature
  2. How This Skill Works
  3. Launch the Reviewer
  4. Handle the Verdict
  5. Write Results
  6. Display Results
  7. What NOT to Do
Sekcje z nagłówków SKILL.md, w oryginale · 138 linii, 811 słów
Podgląd SKILL.md
---
name: plan-verify
description: Use when a plan has been created and needs independent verification against codebase patterns before building
effort: high
allowed-tools: Read, Write, Edit, Glob, Grep, Agent, Bash
argument-hint: "[feature-name]"
---

Verify the implementation plan against the actual codebase.

## Find Active Feature

Feature state is injected by hooks at session start and after compaction — check conversation context for "SHIP ACTIVE FEATURES" or "SHIP FEATURE STATE" blocks first.

1. If `$ARGUMENTS` is provided, use it as the feature name
2. Otherwise, use injected feature state to identify the feature with status `planned`
3. If no injected state is available, fall back to scanning `.planning/features/*/CONTEXT.md`
4. If multiple candidates exist, list them and pick the most recent
5. If no candidates exist, report that no verifiable plans were found

## How This Skill Works

This skill is an orchestrator. The review itself runs in ONE `ship-plan-reviewer` subagent launched via the Agent tool, because the reviewer must be fresh-context: it must not share the planner's conversation, or it inherits the planner's assumptions and rubber-stamps its own reasoning. The skill launches the reviewer, waits for its structured verdict, then writes the results and status itself.

This skill is SINGLE-SHOT: exactly one review round, one verdict, and the user decides what happens next. There is no revision loop here — the automated review → replan → re-review loop lives in `ship/workflows/plan.workflow.js` and runs only under `/ship:go`.

The review contract itself (what the reviewer checks and how it reports) lives in `agents/ship-plan-reviewer.md` — that agent file is its home, and this skill does not restate it.

## Launch the Reviewer

Launch one `ship-plan-reviewer` subagent via the Agent tool with this prompt (substitute `{name}`):

```
Review the plan for feature: {name}

Read .planning/features/{name}/CONTEXT.md and .planning/features/{name}/PLAN.md, then
review the plan against the codebase following your review contract. Return your
plan_review_result block.
```

## Handle the Verdict

Findings are classified by severity:

| Severity | Meaning | Blocks Approval? |
|----------|---------|-----------------|
| **CRITICAL** | Will cause build failure or produce broken code (wrong paths, missing deps, pattern violation that won't compile) | Yes |
| **WARNING** | Inconsistent with codebase patterns, may cause issues | No, but must be noted |
| **SUGGESTION** | Minor improvement opportunity | No |

Overall Status:
- **APPROVED:** No CRITICAL findings. Plan is structurally sound.
- **NEEDS-REVISION:** One or more CRITICAL findings. Plan must be fixed.

### Reviewer failure

If the subagent errors or returns no parseable verdict, relaunch it once. If it fails again, run the **scratch fallback** before giving up: the reviewer writes its record incrementally to `.planning/features/{name}/.review-scratch/plan-round-1.json` (this skill is single-shot, so the record is always round 1), and a reviewer that finished its review but died before reporting has left the whole verdict on disk.

1. Run `git hash-object .planning/features/{name}/PLAN.md` — the only Bash use this skill makes; Bash is in `allowed-tools` for this one command and nothing else.
2. Read `.planning/features/{name}/.review-scratch/plan-round-1.json`.
3. If the file exists, parses as JSON, its `plan_hash` equals the hash from step 1, and `complete` is `true`, adopt its `findings` and `examined` as the verdict (status `APPROVED` when no finding is CRITICAL, `NEEDS-REVISION` otherwise) and continue to "Handle the Verdict" / "Write Results" exactly as for a returned review. In the PLAN.md `## Plan Review` block add the line `**Source:** adopted from the reviewer's scratch record (plan-round-1.json)` under `**Status:**`, so the record shows the verdict was salvaged rather than returned.
4. Otherwise — file missing, unparseable, `plan_hash` mismatched (it reviewed a different plan), or `complete` false — report the failure to the user and stop. A partial record is not a review: never approve a plan without a completed review.

## Write Results

#### If APPROVED:

Update CONTEXT.md frontmatter: set `status: plan-verified`

Append to PLAN.md:

```markdown
## Plan Review

**Status:** APPROVED
**Reviewed against:** [list key codebase files/patterns examined]

### Findings

[Any WARNING or SUGGESTION items — or "No issues found."]
```

#### If NEEDS-REVISION:

Keep CONTEXT.md status as `planned` (do NOT change it).

Append to PLAN.md:

```markdown
## Plan Review

**Status:** NEEDS-REVISION

### Critical Issues

[List each CRITICAL finding with:]
- Task [id] — [issue description]
- Evidence: [what you found in the codebase]
- Fix: [specific recommendation]

### Warnings

[Any WARNING items]

### Suggestions

[Any SUGGESTION items]
```

## Display Results

After writing, display:

```
## PLAN REVIEW COMPLETE

Feature: {name}
Status: APPROVED | NEEDS-REVISION

Codebase patterns checked: [N files examined]
Tasks reviewed: [N] / [N]

[If APPROVED:]
Findings: [N warnings, N suggestions — or "Clean"]
Plan is ready to build.
Next: /ship:build

[If NEEDS-REVISION:]
Critical issues: [N]
- [Issue 1 summary]
- [Issue 2 summary]

Next: /ship:plan {name} (replan with review notes)
```

## What NOT to Do

- **Rubber-stamp.** Never approve without a completed subagent review grounded in codebase exploration.
- **Review in this conversation.** The reviewer must be fresh-context — do not perform the review inline.
- **Rewrite the plan.** You review — the planner rewrites.
- **Block on style preferences.** Only CRITICAL findings block.
- **Invent requirements.** Only check what the plan claims against what the codebase shows.

$ARGUMENTS

Wersje

RepozytoriumWynikLicencja
Ta strona · dilhanz/ship100MIT
xiaolai/vmark90ISC

Migawka bazy z 13.11.2026 · wersja paczki 2d71d2e41dbd (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

  • 100implementation-planning
    Przygotowuje kompletny plan zmiany zachowania w istniejącym kodzie, oparty na aktualnym stanie bazy, zanim rozpocznie się implementacja.
  • 81deep-plan
    Pisze lub poprawia plan wdrożenia dla zatwierdzonego celu deep-work, zanim rozpocznie się implementacja.
  • 100architect
    Tworzy projekt techniczny na podstawie istniejących wymagań, zanim rozpocznie się implementacja.
  • 100context-discovery
    Odkrywa standardy kodowania, wzorce bezpieczeństwa i konwencje projektu, zanim rozpocznie się implementacja.
  • 100verify
    Weryfikuje ukończoną funkcję względem kryteriów akceptacji, w tym testami przypadków granicznych.
  • 100forge-review
    Przeprowadza niezależne, adwersarialne sprawdzenie istniejącego planu wdrożenia, zanim rozpocznie się praca nad produktem.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.