Docs

/ capture

Create a new issue from user input: feature, bug, chore, or idea.

The /capture command creates a new issue. Describe what you need in natural language and FlyDocs handles the rest: determining the issue type, selecting the right project, filling the template, and creating the issue.

Usage

agent chat 
/capture Found a rendering bug in the sidebar, items overflow on mobile
agent chat 
/capture Add a dark mode toggle to the settings page

Or use natural language triggers:

agent chat 
found a bug: the login button doesn't respond on Safari
agent chat 
new idea: let users export their data as CSV

Two Modes

Full Capture

The default mode. FlyDocs determines the issue type from your description (feature, bug, chore, or idea), selects the appropriate project, fills in the issue template, creates the issue via the mechanism scripts, and adds a capture comment.

Quick Capture

For when you want to log something fast and refine it later. Creates a minimal issue with just a title and a triage tag. Defaults to "idea" type. The issue sits in backlog until you run /refine on it.

agent chat 
quick capture: rethink the onboarding flow

What Happens

  1. Type detection: FlyDocs infers the issue type from your description (e.g., "fix" or "bug" signals a bug report, "add" suggests a feature)
  2. Project selection: Routes to the configured active project (primarily cloud tier; local tier uses file-based tracking)
  3. Template application: Fills the appropriate template (feature, bug, chore) to structure the issue
  4. Issue creation: Creates the issue in your issue tracker
  5. Capture comment: Adds a comment documenting the initial capture

When to Use It

Anytime you spot something that needs tracking: a bug you just noticed, a feature idea that came up in conversation, a chore you keep putting off. Capture it now, refine it later.

Related Commands

  • /refine: Triage and flesh out captured issues
  • /activate: Start working on an issue