plan-greenfield

To create a dependency-ordered feature backlog, you must clarify scope, brainstorm across feature domains, and order features by dependencies to produce stack-agnostic specs with acceptance criteria and a sequential build-order roadmap.

Greenfield planning is the process of shaping a new product concept from scratch into a sequential build-order roadmap. You need it when you have a product idea but no existing codebase and require an exhaustive, dependency-ordered feature backlog.

Writing feature specs requires generating template-compliant files in a specs directory that detail user stories, acceptance criteria, edge cases, test scenarios, and open questions for every feature in your dependency-ordered backlog.

Yes, you can generate a product roadmap without an existing codebase by applying greenfield planning. This process forces phase-by-phase product shaping with explicit approvals to produce a breadth, ordering, and depth deliverable.

The best way to structure requirements discovery is through phase-by-phase product shaping. This forces initial scope clarification, broad brainstorming across feature domains, and dependency ordering before writing numbered specs.

No, the generated feature specs are stack-agnostic. They focus on requirements discovery, acceptance criteria, and dependency ordering rather than prescribing specific technical frameworks or platforms.