feature-docs-builderlisted

# Feature Docs Builder Turn a feature idea into a small, durable documentation pack that a human or AI agent can implement later. The output is documents: a spec, design notes, a task plan, ADRs when a decision deserves one, and optionally a single implementation prompt. ## Hard Boundaries - **This skill plans; it never implements.** Do not write feature code, scaffold apps, install dependencies, or run dev servers as part of this skill. - **One-shot app generation is out of scope.** The deliverable is a plan another session or agent executes. - **The only code-shaped output is the implementation prompt**, and only when the user says yes to it. It is still a document. - Create docs only when they preserve decisions, reduce implementation ambiguity, or help future AI/human work. A trivial change needs no doc pack. ## Commands | Command | Description | Reference | |---|---|---| | `plan [feature]` (default) | Plan a feature into a doc pack | Workflow below | | `prompt [feature]` | Build an implementation prompt from an existing plan | [references/implementation-prompt.md](references/implementation-prompt.md) | | `adapt` | Tune this skill to the current project | [references/adapt.md](references/adapt.md) | Routing: no argument → ask what feature to plan. First word matches a command → load its reference; the rest is the target. Anything else → treat the full argument as the feature to plan. ## Preflight Before any planning decision: 1. **Project layer.** If `references/