Command Reference

FlyDocs commands map to stages in the development lifecycle. Type them as slash commands in your AI assistant, or just describe what you want in plain language. FlyDocs recognizes the intent and runs the right procedure.

The Lifecycle

Commands follow a natural progression through the development workflow:

1. /start-session: Begin a work session, get oriented
2. /capture: Create a new issue from input
3. /refine: Triage and flesh out a backlog item
4. /activate: Assign work and transition to In Progress
5. /implement: Build the feature or fix
6. /review: Code review against acceptance criteria
7. /validate: User acceptance testing
8. /close: Move to a terminal state
9. /wrap-session: End the session with a summary

How Commands Work

Commands are natural language. You can type the slash command directly, or just say what you mean:

• /capture or "capture that" or "log a bug" or "new idea"
• /activate or "start work on ENG-145" or "what should I work on"
• /review or "review this" or "code review"
• /wrap-session or "that's it for today" or "let's wrap"

Commands accept natural language arguments. Describe what you need after the command. There are no CLI flags. FlyDocs parses your intent and fills in the details.

What Happens Under the Hood

Each command triggers a defined procedure for that workflow stage. FlyDocs handles the issue operations automatically: creating issues, transitioning statuses, posting comments, assigning work. This works identically whether you're using local file-based tracking or a connected cloud provider.

Agents

Different commands are handled by different agents, each with a focused role:

• PM/Planning Agent: start-session, capture, refine, activate, review, close, wrap-session
• Implementation Agent: implement
• QE/Validation Agent: validate
• All Agents: status

Select a command from the sidebar for detailed documentation, examples, and what to expect when you run it.

---

Questions about commands? Reach out at hello@flydocs.ai.