AcademySkillsDevelopment

spec-flow: spec-driven development in phases

Product and engineering teams that want written specifications and sign-off before a feature is built.

  • Recommendedour rating
  • 33gitHub stars
  • MITlicence
  • 8 months agolast update
git clone https://github.com/echoVic/spec-flow.git
README.md

Loading the file...

What it does

This Claude skill guides a feature from idea to implementation in phases: proposal, requirements, design, tasks and then code. Each phase waits for your confirmation and writes a Markdown document in a .spec-flow folder, which can be committed with the project. You can run it step by step, in batches or phase by phase.

Use cases

  1. 01Write a proposal and requirements for a new feature
  2. 02Keep design documents next to the code
  3. 03Review each phase before implementation starts

Questions about
spec-flow: spec-driven development in phases.

What is spec-flow: spec-driven development in phases used for?

Product and engineering teams that want written specifications and sign-off before a feature is built. This Claude skill guides a feature from idea to implementation in phases: proposal, requirements, design, tasks and then code. Each phase waits for your confirmation and writes a Markdown document in a .spec-flow folder, which can be committed with the project. You can run it step by step, in batches or phase by phase.

How do I install spec-flow: spec-driven development in phases?

Run this in your terminal: git clone https://github.com/echoVic/spec-flow.git

Is spec-flow: spec-driven development in phases open source?

Yes. The code is on GitHub (echoVic/spec-flow) under the MIT licence.

Is spec-flow: spec-driven development in phases safe to use?

It passed our automatic scan for credential theft, hidden instructions and risky install commands. Third party open source software. Sabemos AI does not maintain it. Check the code and permissions before you connect it to company data.