add-feature-specificationlisted

# Feature Specification <!-- uses: - mention: add-feature-discovery - mention: /add.plan - mention: add-product-discovery --> Skill for documenting feature specifications. Creates/updates `about.md` with requirements, business rules, scope and decisions. **Principle:** Document WHAT and WHY, not HOW. ## When to Use - New feature → create `about.md` via questionnaire - `about.md` exists but incomplete → fill missing sections - Requirements changed → update affected sections - Scope expanded → add new requirements, update scope ### When NOT to Use - For technical analysis (use `add-feature-discovery` instead) - For technical implementation planning (use `/add.plan` instead — it writes `plan.md` against the `feature-plan` schema) - For product blueprint / founder discovery (use `add-product-discovery` instead) - For code-level architecture decisions (belongs in discovery/plan, not about.md) ## Workflow **REQUIRED:** Apply before writing: - `token-efficiency` — minified JSON, tables, no decoration - `documentation-style/cache` — Read → Preserve → Complement → Metadata ### Phase 1: Check State (Documental Cache) ```bash cat docs/features/[FEATURE_ID]/about.md ``` | State | Action | |---|---| | Does not exist / empty | Phase 2 (questionnaire) | | Partially filled | Phase 3 (complete) | | Complete | Check if update needed | ### Phase 2: Strategic Questionnaire **Goal:** Extract requirements via structured questions. **Technique:** Infer answers + validate quickly. ``