Stats
Actions
Tags
From feature-driven-flow
Coordinate a structured 7-phase feature delivery workflow for non-trivial feature development. Use when a task needs scoped intent, repository behavior tracing, ambiguity resolution, design choices, controlled implementation, assurance, and end-state reporting.
How this skill is triggered — by the user, by Claude, or both
Slash command
/feature-driven-flow:feature-driven-flowThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Task: $ARGUMENTS
Task: $ARGUMENTS
FDF plugin root: ${CLAUDE_SKILL_DIR}/../.. Resolve shared FDF runtime assets from the first available root in this order:
./fdf/ at the target project rootfdf/ directory (for example %USERPROFILE%\.claude\fdf on Windows or ~/.claude/fdf on macOS/Linux)fdf/ under the resolved plugin root
When running shell reads in PowerShell, wrap filesystem paths in single quotes, especially absolute paths that may contain spaces.
If rg is unavailable, fall back to PowerShell-native discovery such as Get-ChildItem -Recurse -File and Select-String.
Read ${CLAUDE_SKILL_DIR}/behavior.md and follow it exactly.npx claudepluginhub quasarbyte/feature-driven-flow-claude --plugin feature-driven-flowGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.