implement
Installation
SKILL.md
Implement
Execute complete feature implementations using a structured, phased approach with verification gates and atomic commits.
HARD CONSTRAINTS (NON-NEGOTIABLE)
- SCOPE IS LOCKED — Only implement what is in the plan from
/analyze. Nothing more. - NO SCOPE CREEP — Do not implement work from other tickets, even if it seems related or helpful.
- TICKET TRACKING IS MANDATORY — Update ticket status (in-progress/done) as you work.
- EPIC CLOSURE RULES — Never close an epic while child tickets remain open.
- COMMIT BEFORE CLOSE — A ticket status can only be changed to 'done' AFTER the code changes for that ticket have been successfully committed.
- VERIFY BEFORE COMMIT — No code shall be committed until all verification steps (tests, lint, build, etc.) have passed successfully. If any check fails, you MUST resolve the issues and re-verify before attempting to commit.
- NO --NO-VERIFY — Never, under any circumstances, use the
--no-verifyflag with git commit. Pre-commit hooks must always run and pass. If they fail, fix the code. No exceptions, even if explicitly requested. - NO BRANCH CREATION — Never create branches. The agent will already be on the appropriate branch when
/implementis invoked. Do not rungit checkout -b,git branch, orgit switch -c. Work on the current branch.