inline spec
Fix: expired refresh tokens must redirect to /login, not 500. Verify with: pnpm test:run auth-refresh-expired-token
The loop
Start with intent. Add spec, review, checks, and findings only when the work earns them.
- Intent
- Spec
- Implement
- Review
- Check
- Findings
the trivial path first
Most changes stop here.
State one line, implement, run the verification command, paste the output. No file or packet.
spec
loop records
Records between steps
Records move by explicit path and stay beside your harness's artifacts. Promote only the few that belong in the project.
the keys
Intent names the work. Review reconciles the evidence. Findings keep what survives.
the scaffold
Use only what the work earns.
- Task — only when one spec splits.
- Inventory / change plan — for brownfield or structural work.
- Checker — facts and exit codes, never a verdict.
promotion
Move a useful record home. Repair references, validate, then choose whether to commit.
Read the promote skillworkflow / six steps
The loop at a glance.
Six steps around the hexagon; the inscribed triangle is the three keys — intent, review, findings: present on virtually every change, at whatever weight it earns. Work named, evidence reconciled, lessons kept.
- 01Intentcapture the ask
Name the work before it mutates.
- 02Specdefine requirements
Set the bar and how to check it.
- 03Implementrun the change
Do the work. Keep the receipts.
- 04Reviewcompare evidence
Compare the result with the bar.
- 05Checkreport facts
Lint the paperwork. No verdicts.
- 06Findingskeep lessons
Keep the lesson. Bin the rest.
Findings feed the next spec — the loop closes
Run it.
Install the skills — npx skills add jcosta33/suspec-skills -g — and write one spec. The same loop handles the next change.
Source: docs/02-basic-workflow.md