Version: 1.2.1
This repository is a Claude Code marketplace that currently publishes one plugin:
feature-driven-flow
Add the marketplace:
/plugin marketplace add QuasarByte/feature-driven-flow-claude
Install the plugin:
/plugin install feature-driven-flow@quasarbyte-plugins
Optional shared runtime defaults:
- Copy
plugins/feature-driven-flow/fdf/into~/.claude/fdf/if you want one global FDF asset tree outside the installed plugin cache. - Optionally copy
fdf/into a target project root as./fdf/when that project needs local FDF overrides.
feature-driven-flow provides a structured 7-phase workflow for non-trivial software delivery.
After installation, use:
/feature-driven-flow:fdf-start <task>
Claude marketplace commands are documented in namespaced form: /feature-driven-flow:fdf-*.
At runtime, shared FDF assets are resolved from the first available root in this order:
./fdf/in the target project root~/.claude/fdf/- bundled plugin
fdf/
Repo-local overrides still live under .claude/feature-driven-flow/.
.claude-plugin/marketplace.json
plugins/feature-driven-flow/
The marketplace catalog lives at repository root. The actual Claude plugin payload lives under plugins/feature-driven-flow/.
Development happens in QuasarByte/feature-driven-flow. This repository is the Claude marketplace distribution published through QuasarByte/feature-driven-flow-claude.
When using PowerShell to inspect plugin files, quote filesystem paths that may contain spaces.
If rg is unavailable in the shell, use PowerShell-native discovery commands such as Get-ChildItem -Recurse -File and Select-String.
If you use the release scripts from the source repository, PowerShell 7 (pwsh) must be installed.
The .sh and .cmd wrappers still delegate to pwsh.
Scripts that require pwsh:
tools/build-distribution-claude.ps1tools/deploy-distribution-claude.ps1tools/run-validation-cycle.ps1tools/validate-fdf-assets.ps1tools/generate-fdf-manifest.ps1shared/fdf/scripts/convert-effective-instructions.ps1