prd

To turn a feature idea into a product requirements document, you provide a description, batch text, or Markdown sources. The tool converts these into a structured PRD with goals, user stories, functional requirements, and open questions.

Writing user stories with measurable acceptance criteria from a vague feature request involves structuring the input into a PRD. The process extracts goals, functional requirements, and non-goals while explicitly avoiding implementation details.

Yes, you can generate PRDs in batch mode without interactive prompts. Using batch or sub-skill mode flags suppresses prompts, captures ambiguities as open questions, and outputs the final documents deterministically.

To combine multiple Markdown files into a single PRD, use the directory-mode aggregation feature. This process merges combined Markdown sources into one structured document with deterministic ordering.

No, PRD generation explicitly avoids implementation, architecture, or orchestration details. It enforces guardrails to focus strictly on product planning, ensuring outputs remain suitable for later execution without technical constraints.

During spec writing, missing details and ambiguities are handled by capturing them in an explicit Open Questions section. This ensures unresolved requirements are documented rather than guessed during the PRD generation process.