add-feature-discoverylisted

# Feature Discovery <!-- uses: - skill: add-knowledge-discovery - mention: add-architecture-discovery - mention: add-code-review - mention: add-investigation - script: init.sh - script: status.sh --> Skill for technical codebase analysis focused on a specific feature. Persists analysis in `discovery.md` for reuse across sessions. **Principle:** Analyze once, use always. Cache per feature. --- ## When to Use - New feature without `discovery.md` → full analysis - `discovery.md` exists but empty → full analysis - `discovery.md` exists and filled → read cache, complement if needed - Significant codebase changes → update affected sections ### When NOT to Use - Global project analysis (use `add-architecture-discovery` instead) - Post-implementation review of finished work (use `add-code-review`) - Hotfix triage where root-cause investigation is needed (use `add-investigation`) --- ## Workflow **REQUIRED:** Apply before writing: - `token-efficiency` — minified JSON, tables, no decoration - `documentation-style/cache` — Read → Preserve → Complement → Metadata ### Phase 1: Check Cache ```bash cat docs/features/[FEATURE_ID]/discovery.md ``` |State|Action| |---|---| |Filled and recent|Use as context, skip to Phase 4| |Empty/template|Phase 2 (full analysis)| |Outdated|Phase 2 focused on changes| ### Phase 1.5: Past Features Discovery **Goal:** Identify features with direct or indirect relation to the current feature. **EXECUTE as a separate subagent [read-only, light] BE