/ activate
Recommend or assign work and transition to In Progress.
The /activate command gets an issue ready for implementation.
It can recommend what to work on next, or activate a specific issue,
assigning it, setting metadata, and transitioning to In Progress.
Usage
/activate ENG-145 what should I work on next start work on the dark mode issue Two Modes
Recommendation
When you don't specify an issue, FlyDocs queries available issues, ranks them by priority, and suggests the top candidates. You pick one and it proceeds with activation.
Activation
When you name a specific issue, FlyDocs reads it, determines the assignee, assigns the issue, sets any metadata, and transitions it to Implementing.
The Hard Gate
On the cloud tier, assignment is mandatory. FlyDocs will never transition an issue to In Progress without an assignee. The sequence is always: assign first, then set metadata, then transition. The local tier is more relaxed; assignment is still recommended but not strictly enforced.
What Happens
- Read the issue: Loads the full issue context
- Determine assignee: Identifies who should own the work
- Assign: Sets the assignee on the issue
- Set metadata: Updates any additional fields needed
- Transition: Moves to Implementing with a status comment
When to Use It
After /start-session when you're ready to pick up work. Or
anytime you want to switch to a different issue. If you're not sure what
to work on, just ask. The recommendation mode will guide you.
Related Commands
/implement: Build the activated issue/status: Check current state/refine: Refine before activating