spec-startlisted
Install: claude install-skill DahanItamar/spec-architect
# Spec Start
**Stage 0 of 6 — the front door.** This skill writes nothing and decides nothing. It looks at what
the repository already has, tells the user where they are in the chain, and hands them one command.
Its whole reason to exist: six commands in a picker give a user no way to tell which one begins,
and the wrong entry wastes a whole stage. `/spec-tasks` on a repo with no spec produces nothing but
an error, and `/spec-architect` on a repo that already has a spec silently rewrites the reasoning
that made the first version correct.
---
## Always print the map first
```markdown
> **The spec chain**
>
> `1 constitution` → `2 spec` → `3 tasks` → `4 implement` → `5 drift` → `6 refactor` → *(loops back to 2)*
>
> | Stage | Command | Produces | Run it when |
> |:-:|---|---|---|
> | 1 | `/spec-constitution` | `docs/CONSTITUTION.md` | The repo's rules live only in your head. **Optional** |
> | 2 | `/spec-architect` | `docs/SPEC.md` | You have an idea, or a change to an existing spec |
> | 3 | `/spec-tasks` | `TASKS.md` | A spec exists and you want an ordered build list |
> | 4 | `/spec-implement` | code | A task list exists with unchecked boxes |
> | 5 | `/spec-drift` | a report | Code and spec may have diverged |
> | 6 | `/spec-refactor` | `docs/refactorings/NNNN/` | The code is right and the shape of it is what hurts. **Optional** |
```
## Then look, and route
Check the repository — do not ask the user what it contains, because the whole point is that they
may not know