← ClaudeAtlas

developlisted

Run /develop to build a feature from its spec. Stops and routes to /architect if building would mean inventing a decision no spec records. Never runs migrations, never invents a business rule.
rishabhsisodiya/stop-guessing · ★ 0 · AI & Automation · score 70
Install: claude install-skill rishabhsisodiya/stop-guessing
## What this skill does Builds one feature from its spec, and refuses to build one that has no decision behind it. `/architect` writes the decision down. This skill is what makes writing it down matter: it reads the spec, builds exactly what the acceptance criteria require, checks its own work, and ticks the milestones in the scope. When there is no spec and building would mean inventing something, it stops. ## The gate Before writing any code, apply the **invent test**: > Would building this mean deciding something the engineer has not decided? Yes for: a provider or library choice, a data model or a new column, a cross cutting pattern, a whole page with no design, a business rule, a permission rule, a pricing or ordering or ranking rule, an error contract, anything to do with money or personal data. No for: pure implementation that an existing spec, `design.md`, or a convention already recorded in `AGENTS.md` fully determines. **Unsure means yes.** An unflagged decision is the expensive miss, and it is the reason this collection exists. ### Calibration: what must stop, and what must not A gate that stops too often is worse than no gate, because the engineer learns to override without reading, and then it stops nothing. Use these to keep the bar in the right place. **Stop.** Each of these decides something the engineer has to live with: - The spec says "store the user's preferences" and names no fields. What shape? - Nothing says whether a deleted record is soft