implement-features-cx

# /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. ## Codex Execution Notes - Treat `// turbo` / `// turbo-all` as instructions to use `multi_tool_use.parallel` for independent reads, checks, and GitHub calls. - Approval gates (Phase 3 and Phase 4 → 5) are hard stops. Present the report/plan in the final response and do not move to implementation phases until the user explicitly approves. - Keep harvest/research bounded enough to produce the approval report quickly; do not start implementation while still in report phases. - The trust-but-verify audit in Phase 5.2 is mandatory before any commit — full lint + typecheck + cycles + build + coverage, plus a real `git diff` review for out-of-scope changes. - Phase 1.7 stale-reclaim (15-day rule) is opt-in per run: only execute when the user asks for a "reclaim pass" or when the harvest report explicitly flags eligible IN FLIGHT / NEEDS DETAIL items. **Output directory structure:** ``` _ideia/ ├── viable/ # ✅ Approved, awaiting implementation │ ├── 1046-native-playground.md │ └── 1046-native-playground.requirements.md ├── implemented/ # ✅ Implemented but rel...