/ implement
Build the feature or fix, following the implementation checklist.
The /implement command starts the build phase. It loads the
issue context, project standards, and relevant skills, then guides you
through an incremental implementation against the acceptance criteria.
Usage
/implement build this pick up ENG-145 What Happens
- Load context: Reads the issue, project standards, and any relevant installed skills
- Show implementation checklist: Presents the acceptance criteria as a working checklist
- Implement incrementally: Writes code, writes tests, and updates the checklist checkboxes in the issue description as criteria are met
- Document decisions: Posts significant decisions and trade-offs as issue comments
- Simplify and self-review: Cleans up the code before handoff
- Hand off to review: Transitions the issue to Review with an implementation summary
Key Rules
- Checkboxes live in the issue description, never in comments. Progress tracking happens by updating the description, so the checklist is always the single source of truth.
- Every TODO gets a tracked issue. If something comes up during implementation that's out of scope, capture it as a separate issue.
- Transitions include an implementation summary. No silent status moves. Every transition gets a comment explaining what was done.
The Implementation Flow
Work happens conversationally. You and the AI assistant collaborate on the build, discussing approaches, writing code, running tests. The implementation agent follows your project's installed skills and coding standards throughout.
When all acceptance criteria checkboxes are checked, the implementation agent does a self-review pass to simplify the code, then transitions the issue to Review.
When to Use It
After activating an issue with /activate. The issue needs to
be in the Implementing state with an assignee. If you say "implement"
without an active issue, FlyDocs will prompt you to activate one first.
Related Commands
/activate: Activate an issue first/review: Review when implementation is done/wrap-session: Wrap if you need to stop mid-implementation