ralph-init

To generate a structured PRD, provide a project or feature description to initiate an interactive interview or direct conversion. The tool outputs a canonical requirements document with problem statements, goals, and acceptance criteria.

A canonical PRD reduces planning waste by formalizing product goals and testable acceptance criteria upfront. This single structured document guides execution loops, removing ambiguity and preventing scope drift during development.

Yes, you can create a PRD through an interactive interview process. The tool gathers your project requirements conversationally and converts them into a structured requirements document without needing manual formatting.

The best way to structure requirements for iterative development is using a canonical PRD format. This includes defining problem statements, goals, non-goals, technical constraints, and phased implementation steps as completion criteria.

You can track progress against a product plan using a canonical progress ledger. Initializing the PRD automatically creates a JSON ledger file to monitor goal-driven iterations and execution status throughout the session.

No, an active session is not strictly required as the tool ensures backward compatibility for legacy inputs. However, if an active session exists, the progress ledger is initialized directly within that specific session scope.