- Agent Instructions  Read this file first when working on this feature. </template> <template file="CLAUDE.md"> @AGENTS.md </template> <template file="design.md"> # <Title> - Design  </template> <template file="implementation.md"> # <Title> - Implementation ## Status - **Phase**: design - **Blocked**: no ## Done ## Next - [ ] Define the technical approach ## Context </template> <template file="decisions.md"> # <Title> - Decisions  </template> <template file="future-work.md"> # <Title> - Future Work </template> <template file="examples/TEST_LOG.md" condition="feature produces executable code"> # <Title> - Test Log  </template> </templates> ### /spec status Read and display `specs/INDEX`. If missing, scan `specs/*/implementation.md` to rebuild it. </article></body></html>

--- name: spec description: Create feature specs for context continuity across agent sessions. Use when starting a new feature or when user runs /spec new. --- # /spec - Feature Spec Management ## Commands ### /spec new Creates a feature spec directory with standard template files. lowercase name, replace spaces with hyphens → `` error if `specs//` exists `specs//` write all templates below to `specs//` create `examples/` with TEST_LOG.md fill AGENTS.md from conversation context (overview, key files, quick start) append row to `specs/INDEX` (create with header `slug\tphase\tblocked\tdesc` if missing)

spec

Scan your own AI components