six points / six steps
Pull · Spec · Task · Run · Review · Close
The mark follows the process: each point creates or checks the record the next point needs. Inventory and Change Plan appear when the work is brownfield or structural.
The loop
Pull → Spec → Task → Run → Review → Close. Six steps, six files to inspect, and a clearer handoff between agent work and review.
note
01
Pull
Copy the ticket into an intake file verbatim — unedited, uninterpreted. The spec is where you interpret; the intake just preserves what was actually asked, so it still anchors you after the upstream ticket changes or disappears.
pwrcheckevidence
intake/INTAKE-42.md## INTAKE-42 — Add dark mode to marketing site
- Requested by: design
- Scope: homepage and global shell only
- Deadline: launch week
- Links: SPEC-design-system, CHANGE-website-launch
02
Spec
Write requirements one per ID, each with a verification method. If you cannot check it, keep editing.
pwrcheckevidence
specs/shell/spec.md### AC-003 — Global shell includes nav and footer
A Shell component renders on every route via app/layout.tsx.
- Nav: logo, links, mobile hamburger below lg.
- Footer: copyright, links, colophon line.
Verify with: npm run build passes; every generated page contains
exactly one <nav> and one <footer>.
03
Task
Hand the agent a bounded packet: what to change, what not to change, and how to verify.
pwrcheckevidence
tasks/TASK-shell.md## TASK-shell
Scope: implement Shell component per AC-003.
Do not change: homepage content, analytics.
Verify:
- npm run build passes
- grep finds 1 <nav> and 1 <footer> per page
04
Run
The agent implements and pastes real evidence — command output, screenshots, links — next to each requirement.
pwrcheckevidence
tasks/TASK-shell.md$ npm run build
✓ Compiled successfully
Route (app): /, /kitchen-sink
$ grep -o '<nav>' out/index.html | wc -l
1
05
Review
Check evidence per requirement. Human attention goes only where the evidence is missing or ambiguous.
pwrcheckevidence
reviews/REVIEW-shell.md| AC | Result | Evidence |
|-------|-------------|---------------------------|
| AC-003| Pass | 1 nav, 1 footer found |
| AC-009| Unverified | manual resize pending |
06
Close
Merge the change, save findings so the next session can use them, and update the board.
pwrcheckevidence
findings/FINDING-tailwind-v4-syntax.md## FINDING-tailwind-v4-syntax
When adding custom keyframes in Tailwind v4, use plain CSS
classes rather than escaped utility prefixes to avoid PostCSS
parse errors.
Ready to run it?
Copy the starter kit and write your first spec. The loop is the same on day one as on day one hundred. Findings make the next pass a little less annoying.