implement-features-cc

# /implement-features — Feature Request Harvest, Research & Implementation Workflow ## Overview A **5-phase** workflow that systematically harvests feature requests from GitHub issues, creates structured idea files, researches solutions across the internet and Git repositories, presents a consolidated report for user approval, then generates detailed implementation plans and executes them. **Output directory structure:** ``` _ideia/ ├── viable/ # ✅ Approved, awaiting implementation │ ├── 1046-native-playground.md │ └── 1046-native-playground.requirements.md ├── implemented/ # ✅ Implemented but release PR not yet merged to main (transient) │ └── 1046-native-playground.md ├── need_details/ # ❓ Issue OPEN — awaiting author clarification (permanent archive) │ └── 1015-warp-terminal-mitm.md ├── defer/ # ⏭️ Issue CLOSED — good idea, deferred for future cycles (permanent) │ └── 1041-smart-auto-combos.md ├── notfit/ # ❌ Issue CLOSED — out of scope (permanent) │ └── 945-telegram-integration.md ├── exists/ # 🔁 Issue CLOSED — feature already shipped (permanent, kept separate from notfit) │ └── 812-rate-limit-dashboard.md └── in_flight/ # 🚧 Issue OPEN — third-party PR already addresses it (permanent until reclaim or merge) └── 988-batch-export.md _tasks/features-vX.Y.Z/ # Implementation plans (per-release) └── 1046-native-playground.plan.md ``` > **LIFECYC...