Docs

Command reference: 19 FlyDocs slash commands

Full command reference for FlyDocs slash commands: 19 commands covering sessions, issues, workflow, and setup.

FlyDocs provides 19 slash commands that map to stages in the development lifecycle and supporting workflow operations. Type them as slash commands in your AI assistant, or describe what you want in plain language -- FlyDocs recognizes the intent and runs the right procedure.

Session Commands

Manage work sessions -- start, monitor, and wrap up.

Command Description
/start-session Begin a work session. Loads project context, shows active and blocked issues, and helps you pick what to work on.
/wrap-session End the current session with a structured summary. Posts a project update, prompts for knowledge capture.
/status Show issue counts by status for active projects. Available at any point during a session.

Issue Lifecycle Commands

Move issues through the full development lifecycle, from initial capture through implementation and close.

Command Description
/capture Create a new issue from natural language input. Detects type (feature, bug, chore, idea) and fills the appropriate template.
/refine Triage and flesh out a backlog item. Add acceptance criteria, set priority and estimates, assign labels.
/activate Assign work and transition an issue to In Progress. Sets up the session context for implementation.
/implement Build the feature or fix. Works through acceptance criteria, writes code and tests, posts progress comments.
/review Code review against acceptance criteria. Checks code quality, test coverage, and spec compliance.
/validate User acceptance testing. Verifies the implementation meets the spec from a QE perspective.
/close Move an issue to a terminal state. Archives the completed work.

Workflow Commands

Supporting operations for common workflow needs.

Command Description
/block Flag the current issue as blocked with a reason. Pauses the session and notifies relevant people.
/attach Attach to a different issue mid-session. Loads its context without changing status.
/knowledge Capture decisions, notes, or feature documentation that persists across sessions.
/project-update Post a structured project status update with progress, blockers, and next steps to your PM tool.

Setup Commands

Project orientation, configuration, and maintenance.

Command Description
/onboard The single setup-and-orientation command. On first run, generates project context using your IDE agent (no API key needed). On subsequent runs, presents a comprehensive project overview.
/new-project Create a new project with context, configuration, and issue tracking scope.
/flydocs-update Pull the latest skills, hooks, commands, and configuration from the server.

Upgrading a project from local to cloud is no longer a slash command. Run flydocs connect from the terminal — see Upgrading from local to cloud.

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, onboard, new-project, project-update
  • Implementation Agent: implement
  • QE/Validation Agent: validate
  • System: flydocs-update
  • All Agents: status, block, attach, knowledge

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

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