---
description: FlyDocs development lifecycle — stages, gates, and workflow rules
alwaysApply: true
---

<!-- Condensed from .claude/skills/flydocs-workflow/SKILL.md — update both when
     changing patterns. Shipped from template/.cursor/rules/, not derived at
     install time: the Cursor tree is exactly what the template carries. -->

# FlyDocs Workflow

## Golden Rules

1. Every status transition gets a comment — no silent moves
2. Assignment required before In Progress
3. Checkboxes live in issue description, never comments
4. Use workflow scripts for all issue operations — execute, don't describe
5. Session wrap posts a project update
6. Product scope filtering — only show projects/issues matching config labels

## Lifecycle

```
Capture → Refine → Activate → Implement → Review → Validate → Close
                                 ↕
                              Blocked
```

## Stage Index

| Stage | File | Agent |
|-------|------|-------|
| Capture | stages/capture.md | PM |
| Refine | stages/refine.md | PM |
| Activate | stages/activate.md | PM |
| Implement | stages/implement.md | Implementation |
| Review | stages/review.md | Review |
| Validate | stages/validate.md | QE |
| Close | stages/close.md | PM |

## When This Applies

These rules apply to **issue operations and status transitions only** — not
general coding. For building features, fixing bugs, and writing code, skip
this and just do the work.

## Intent Mapping

- "create/capture/log an issue" → Capture stage
- "triage/refine/spec out" → Refine stage
- "start work/activate/assign" → Activate stage
- "close/ship/done" → Close stage
- "start session/wrap session" → Session management

Dispatcher scripts handle all issue operations — see the workflow skill's
scripts directory. Slash commands load stage files automatically.