implementlisted

# implement — spec-driven implementation Methodology for implementing against written specs, leaving durable evidence, and closing the loop with review. Loaded by the `smith` agent; usable directly. ## Document layout — three axes Every artifact this skill produces goes to exactly one of three roots, split by **lifetime**, not by who wrote it: | Root | Lifetime | Test | Authority | |---|---|---|---| | `docs/` | Permanent, cumulative | Must still be true in 6 months | **Norms, ratified by humans.** Read when the repository has them; **never created here** — a project's documentation convention is its own | | `specs/` | One work item | Its role ends when this work ships (SDD, overview) | The contract this work executes against. A human approves `plan.md`, which is why this is a repository document and not tool state | | `.specseal/` | Mixed — see below | Everything this plugin maintains | Written and read by machines: the map, the migration config, the follow-up list, task lists | The axis is lifetime and authority, **not audience** — humans and AI read all three. (Labeling policies "for humans" would push sessions away from reading them, and policy outranks everything else when a repository has it.) `.specseal/` is committed — gitignored files do not follow worktrees or other machines — and its existence is what tells the gates this repository runs the workflow. Inside it, lifetimes differ: ``` .specseal/ ├── map.md permanent — spec clause ↔ code coordinates