cofin/flow-planning
skills/flow-planning/SKILL.md
Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
$ install --global
skillsauthnpx skillsauth add cofin/flow flow-planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 5:25 AM55.6s2 files scanned
SKILL.md
- name:
- flow-planning
- description:
- Use when drafting PRDs, researching, planning, refining, revising, or creating .agents/specs/<flow_id>/spec.md worksheets for Flow.
Flow Planning
Use this lifecycle skill for PRDs, research, single-flow planning, refinement, revisions, and task creation.
Workflow
- Read project context, patterns, knowledge chapters, and relevant existing specs before asking questions.
- Research code paths and external APIs before locking implementation decisions.
- Create PRDs as roadmap epics and single-flow specs as implementation worksheets.
- Refine until tasks include concrete files, behavior, tests, commands, and acceptance criteria.
- 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
- Plan
- Research
- Refine
- Revise
- Task
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
cofin/flow-sync-status
testing
VerifiedTrustedCommunity
Use when syncing Beads state to markdown, checking Flow status, refreshing context docs, validating task markers, or reporting ready/blocked Flow work.
11SKILL.mdUpdated Apr 27, 2026
cofin/flow-setup
testing
VerifiedTrustedCommunity
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.
11SKILL.mdUpdated Apr 27, 2026
cofin/flow-execution
testing
VerifiedTrustedCommunity
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.
11SKILL.mdUpdated Apr 27, 2026
cofin/flow-completion
tools
VerifiedTrustedCommunity
Use when reviewing, finishing, archiving, reverting, validating, or cleaning up Flow work after implementation or phase completion.
11SKILL.mdUpdated Apr 27, 2026