Build Feature

• Find similar features already built — follow their patterns
• Check /src/lib/ for existing utilities before writing new ones
• Read the relevant controller / service / route files

Present the implementation plan

Structure the plan as:

1. New files — name, purpose, what it exports
2. Existing files to modify — what changes and why
3. Types/interfaces — define them explicitly upfront
4. Test files — what will be tested and how
5. Sequence — build order (dependencies first)

Ask: "Does this plan look right? Any changes before I start building?" Wait for confirmation before writing any code.

Use Plan Mode for this step — stop and re-plan if the approach isn't working.

Phase 2: BUILD (test-first)

Write tests before implementation

For each piece of logic:

1. Create the test file
2. Write tests describing expected behavior — they will fail initially (that's correct)
3. Implement to make the tests pass

# Confirm tests fail before implementation (expected)
npm test -- --testPathPattern=[test-file] 2>&1 | tail -20

Implement

• No any types — use unknown and narrow, or define proper types
• Controller → Service → Prisma (3-layer pattern — never business logic in controllers)
• Handle all error cases explicitly — no bare try/catch swallowing errors
• Use the project logger, never console.log
• Check /src/lib/ before writing new utilities

Type-check and lint as you go

After each logical chunk:

npm run typecheck 2>&1 | tail -20
npm run lint 2>&1 | tail -20

Fix errors immediately — never let them accumulate.

Phase 3: VERIFY

Run the full quality suite

/verify

All checks must pass. Fix anything failing before proceeding.

Audit acceptance criteria

Go through each criterion from the issue and confirm it is met:

Acceptance Criteria Audit:
✅ [Criterion 1] — verified by: [test name or observable behavior]
✅ [Criterion 2] — verified by: [test name or manual check]
⚠️  [Criterion 3] — UNMET: [what's missing]

If any criterion is unmet, do not proceed — address it first.

Phase 4: COMMIT

git add [specific files — never git add -A without reviewing]
git commit -m "feat([scope]): [what was built]

- [Key change 1]
- [Key change 2]

Refs #$ARGUMENTS"

The pre-commit hook runs lint-staged automatically.

Phase 5: PUSH

git push

Check CI:

gh pr checks

Update the draft PR body with what was built and which acceptance criteria are met.

Summary

Report:

• Files created/modified
• Tests written (count)
• Acceptance criteria status (all ✅ or note what's pending)
• CI status
• Next: /human-test $ARGUMENTS for human validation, then /pr-prep $ARGUMENTS