Guide feature delivery through DDD, BDD, TDD, and Git phases.
npx skills add https://github.com/mikivujkovic/claude-feature-flow --skill feature-flow
Please help me install this Agent Skill. Skill: feature-flow Source: https://github.com/mikivujkovic/claude-feature-flow/tree/main/.claude/skills/feature-flow Command: npx skills add https://github.com/mikivujkovic/claude-feature-flow --skill feature-flow
This Skill guides users through a code-agnostic, interactive flow to implement a feature using DDD → BDD → TDD → Git, reducing manual coordination and cognitive load.
Start a new feature with /feature:start "Feature name" and progress through the stages with the /feature:next, /bdd:feature, /tdd:plan, and /feature:accept as you confirm at each step.
High-intent search queries and answers about installing and using this skill.
Feature-flow guides you through an end-to-end DDD → BDD → TDD → Git workflow. Start with /feature:start, define domain rules with a DDD partner, outline scenarios with BDD, generate a TDD plan, then accept and commit. The Skill tracks state and prompts you at each phase, eliminating manual coordination across stages.
Yes, feature-flow is code-agnostic and works with any language or framework. It focuses on the conceptual flow—domain design, behavior definition, and test planning—rather than language-specific implementation, so your tech stack doesn't constrain the process.
Feature-flow automates the progression: use /bdd:feature to refine scenarios from domain notes, generate a /tdd:plan from those scenarios, then validate with /feature:accept. This structured handoff ensures acceptance criteria directly inform test design without manual translation.
Feature-flow maintains a feature-state.json file that records your current position through DDD, BDD, TDD, and Git phases. This persistent state eliminates context loss and lets you resume or review progress at any point in the workflow.
No—Git integration is optional and guided. Feature-flow prompts you through /feature:accept and provides auto-commit guidance, but you control when and whether to commit. The core DDD → BDD → TDD flow works independently of version control.
thapaliyabikendraConvert stakeholder needs into structured, testable specifications with Markdown output.
infraspecdevImplement features with acceptance-criteria-driven development and test-first delivery.
elihunter173Create and switch to git branches with standardized naming conventions.
ValorVieGuide ATDD specification workshops, distillation, development, and demos.
