implement-featurelisted

# Implement Feature Implement an **approved** implementation specification. This skill does **not** know or care where the specification came from. It may be ClickUp, Jira, GitHub Issue, Markdown, a PRD, or a Design Contract plus tickets. The process is identical; only the execution engine changes. ## Supported execution engines | Engine | When to use | |--------|-------------| | Codex | User says `/implement codex` or "use Codex" | | Cursor | User says `/implement cursor`, default in Cursor Agent, or "use Cursor" | | Claude Code | User says `/implement claude` or "use Claude Code" | Keep the workflow identical across engines. Do not invent engine-specific product steps. ## Inputs - Implementation specification (required) - Optional: ClickUp URL / task id - Optional: repository issue (GitHub or GitLab) - Optional: repository / base branch - Optional: execution engine preference ## Workflow Copy and track: ```text Implement feature progress: - [ ] 1. Read specification - [ ] 2. Validate completeness - [ ] 3. Read project guidance - [ ] 4. Inspect nearby code - [ ] 5. Create an implementation plan - [ ] 6. Create a sibling worktree and branch - [ ] 7. Implement - [ ] 8. Run lint, typecheck, tests, build - [ ] 9. Review against acceptance criteria - [ ] 10. Submit change request (PR/MR + CI wait) - [ ] 11. Update tracker (ClickUp and/or repo issue if linked) ``` ### 1. Read specification Load the full specification from the provided source. Prefer the linked task or