flow-planning
Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
Best use case
flow-planning is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
Teams using flow-planning should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/flow-planning/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How flow-planning Compares
| Feature / Agent | flow-planning | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Flow Planning Use this lifecycle skill for PRDs, research, single-flow planning, refinement, revisions, and task creation. ## Workflow 1. Read project context, patterns, knowledge chapters, and relevant existing specs before asking questions. 2. Research code paths and external APIs before locking implementation decisions. 3. Create PRDs as roadmap epics and single-flow specs as implementation worksheets. 4. Refine until tasks include concrete files, behavior, tests, commands, and acceptance criteria. 5. Create Beads epics/tasks and sync markdown views according to policy. ## Guardrails - Planning must be decision-complete; do not defer obvious research to implementation. - Ask only product or tradeoff questions that cannot be answered from the repo. - Store plans under `.agents/specs/<flow_id>/`, not ad hoc docs paths. - Do not modify production code during planning. ## Validation - Confirm every requirement maps to an implementation task and test scenario. - Confirm tasks are small enough for a low-context executor to complete without guessing. - Run spec review or code-reviewer validation before presenting final planning artifacts when available. ## References Index - [PRD](../flow/references/prd.md) - [Plan](../flow/references/plan.md) - [Research](../flow/references/research.md) - [Refine](../flow/references/refine.md) - [Revise](../flow/references/revise.md) - [Task](../flow/references/task.md) ## Example User: "Plan skill trigger optimization." Action: inspect current skills and validators, ask unresolved product tradeoffs, create a Flow spec with Beads tasks, and refine until the implementation path is explicit.
Related Skills
flow-memory-keeper
Use at task, phase, flow, sync, archive, finish, revise, or failure checkpoints to keep Flow specs clean, capture learnings and failures, elevate durable patterns, and refine this skill with project-specific nuances
flow
Use when a repository has .agents, when the user asks for Flow lifecycle routing, Beads-backed task memory, spec-first planning, TDD implementation, sync/status, review, finish, archive, or /flow:* help.
flow-sync-status
Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.
flow-setup
Use when initializing Flow in a repo, configuring .agents, installing or checking Beads bd, setting local-only sync policy, or creating first project context files.
flow-execution
Use when implementing Flow tasks from Beads or spec.md, claiming ready work, applying TDD, recording task notes, committing, and syncing after task state changes.
flow-completion
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
vue
Use when editing Vue projects, .vue files, vue.config.js, Vue 3 components, Composition API, <script setup>, SFC state, deployment workflows, or Vue CI configuration.
vite
Use when editing Vite projects, vite.config.ts, vite.config.js, Vite plugins, HMR, asset bundling, frontend build settings, deployment config, or Litestar/Vite integration.
uvicorn
Use when deploying ASGI apps with uvicorn, editing uvicorn CLI commands, Config or Server usage, workers, reload, event loop selection, SSL, lifespan, logging, or development server behavior.
tracer
Use when tracing execution paths, mapping dependencies, understanding unfamiliar code, following data flow, investigating end-to-end behavior, debugging call chains, or deciding which files to read next.
testing
Use when writing or refactoring tests, editing test_*.py, *.test.ts, *.spec.ts, conftest.py, vitest.config.ts, pytest fixtures, mocks, coverage, async tests, anyio, or test failure debugging.
terraform
Use when creating, adopting, refactoring, or operating Terraform, *.tf files, .terraform.lock.hcl, terragrunt.hcl, root modules, backends, state, workspaces, imports, CI plan/apply, tests, or policy checks.