parse-prd

To convert a product requirements document into an executable spec, paste the PRD text or provide a file path. The tool extracts goals, acceptance criteria, and user stories to generate a structured .autopilot/spec.md file with hierarchical tasks.

SPARC annotation in project planning is a method used to map extracted PRD features into hierarchical tasks with dependencies. It structures the generated spec.md to ensure downstream teams understand complexity estimates and execution order.

Yes, you can generate a task list with complexity estimates directly from a PRD. By parsing sections like Objectives and User Stories, the tool produces a buildable spec.md containing mapped dependencies and SPARC-mode annotations.

To resolve ambiguities when generating specs from PRDs, the tool provides specific guidance alongside the output spec.md. It highlights unclear requirements extracted from the source document so you can refine goals and acceptance criteria before building.

If an existing spec.md file is present in the autopilot directory, the tool issues a warning before overwriting it. This precaution prevents losing previous structured specs and task lists when parsing a new product requirements document.