spec-firstlisted
Install: claude install-skill Udhay-Adithya/skills
# Spec first
Write the specification before the code. The spec is the shared source of truth: what is
being built, why, and how anyone will know it is done. Code without one is a guess that
happens to compile.
## When to skip this
A one-line fix. A typo. A change where the requirement is unambiguous and self-contained.
A spec for those is ceremony.
Everything else: a new feature, a change across several files, an architectural decision,
anything that would take more than half an hour. A simple task does not need a *long*
spec, but it still needs acceptance criteria, and a two-line spec is a real spec.
## The gate
```
SCOPE CHECK -> SPECIFY -> PLAN -> TASKS -> IMPLEMENT
| | |
approval approval approval
```
**Do not advance a phase without approval.** The whole value is in the stop.
## Phase 0: scope check
Most requests describe one capability. If this one does, skip straight to Specify. This
phase is for the exception.
Decompose first when one requirement bundles several independently testable capabilities:
- It names distinct capabilities with their own consumers or their own data.
- The acceptance criteria cluster into groups that could ship and be verified separately.
- One capability could be cut or swapped without rewriting the others' requirements.
Then propose a map before writing any spec. A table and a build order, not a project plan:
```markdown
# Capability map: <initiative>
| Module | Responsibility | De