add-feature-specificationlisted

# Feature Specification <!-- uses: - skill: add-doc-schemas - command: /add.new - mention: /add.brainstorm - mention: add-feature-discovery - mention: /add.plan --> **The single writer of `about.md`.** `/add.new` loads it, whether the user ran `/add.new` by hand or `/add.brainstorm` handed off to it on an automatic delivery. Both arrive at the same command, so both produce the same document from the same rules. **Principle:** Document WHAT and WHY, not HOW. ## When to Use - Writing or completing `about.md`. - Requirements changed, or scope expanded, and the document must follow. ### When NOT to Use - Technical analysis of the codebase — that is `add-feature-discovery`. - Technical implementation planning — that is `/add.plan`, which writes `plan.md`. - Allocating a feature id, creating its directory, running the schema gate or dispatching a reviewer. **All four are orchestration and belong to the command that loaded this skill**, never here. A skill that allocates an id behaves differently depending on who called it, which is the one thing a single writer exists to prevent. --- ## Phase 1: Check State Read `docs/features/[FEATURE_ID]/about.md`. | State | Action | |---|---| | Does not exist / empty | Phase 2 | | Partially filled | Phase 2, for the missing sections only | | Complete | Phase 2 decides whether anything changed | ## Phase 2: Read the Intent File, Then Ask Only What It Left Open **The calling command resolves the intent file and hands it over.**