ralph-plan

To decompose a feature request into actionable stories, you write a feature brief or user need. The tool then generates a structured PRD.json with 5-15 atomic stories, each including dependencies, acceptance criteria, and tests for incremental delivery.

A PRD.json schema for agile backlog planning documents a feature, description, created timestamp, and a structured list of stories. Each story entry includes an id, title, description, status, depends_on, files, acceptance_criteria, and tests to guide development.

Structuring story dependencies for parallelizable implementation requires validating sequencing rules to prevent circular dependencies. This ensures early milestones are clear and acceptance criteria are met before dependent stories begin.

Yes, you can automatically generate a product requirements document with acceptance criteria and tests by providing a feature brief. The output is a PRD.json containing 5-15 atomic stories, each with defined acceptance criteria and tests.

The best way to break down a large feature into 5-15 independent stories is to validate sequencing rules and enforce a strict PRD.json schema. This prevents circular dependencies and ensures clear acceptance criteria for safe, parallelizable implementation.