docs-feature-planning-spec
Installation
SKILL.md
Rule
For a feature substantial enough to need a plan before code, write it as a single doc with these sections, in this order:
# <Feature Name> — Concept
> Status: Draft / Planning · Owner: <you> · Last updated: <date>
>
> One or two sentences on what this plans and its current state —
> "no code has been written yet" or "phase 1 is live, this covers phase 2."
## 1. Goal
What this feature does and why, in a few sentences. Name who it's for
and what changes for them.
### Design principles