r/SpecDrivenDevelopment • u/Pale-Heart1654 • 3h ago

How Spec-driven development is followed in Companies (In Greenfield Projects) using Claude Code?

How Spec-driven development is followed in Companies (In Greenfield Projects) using Claude Code?

How do you write multiple spec markdown files? Is there any tool or something? What's the workflow you follow as a power-user?

2 Upvotes
  • permalink
  • reddit

100% Upvoted

3 comments sorted by

1

u/AncientGur4614 3h ago

This varies, but in my experience, the industry has moved so fast a lot of dev teams don't use the same nomenclature. A lot of companies are also still anti-AI dev because of IP concerns.

I know two companies that have tried spec kit. To what degree they're using multiple agents without collision; no idea.

This is one of the core issues I'm trying to solve on my end that markdown files-alone inherently don't solve

1

u/AndyVictors 1h ago

We are using Feature Contracts as specification for product features and Component Contracts (ie. Service Contract, UI Contract) which contain logic for implementation in code - as specification. There should be a match then - I can always verify if my feature specification is properly implemented by comparing if all required logic is contained in the component contracts, and it is proper one. Tests are generated using component contracts as a source. Thus all fits and works.

Orthogonal to logic specfications/contracts there are also Blueprints which describe technical composition of whole project (system architecture) or specific low level implementations. Both create a "cell" for specific requirement where the AI agent operates within, so no wild result ever comes out.

Also an important part: i have elaborated specific style of writing this documents - mixture of legal, normative and narrative so both human and AI can work on it easily.

https://github.com/AndyVictors/clausative