What problem does it solve?
Converts unstructured product requirements documents (files, URLs, or pasted text) into a standardized, machine-readable project foundation so downstream planning and review workflows can run reliably without manual reformatting.
Core Features & Use Cases
- Input ingestion: Accepts file paths, URLs, or pasted text and saves the canonical source to .context/prd.md.
- Structured analysis: Parses content into eight categories (overview, domain model, architecture, milestones, features, technical requirements, risks, open questions) using explicit extraction and marked inferences.
- Atomic decomposition & artifacts: Produces a requirements JSON with R-IDs, MoSCoW priorities, acceptance criteria, and search hints, plus a project-overview markdown that downstream skills consume.
- Clarification flow: Prioritizes and prompts the user with top clarifying questions and updates artifacts based on answers.
- Persistence & integration: Writes .context/spec/requirements.json and .context/project-overview.md and optionally registers artifacts with the pixl CLI if available.
Quick Start
Analyze the provided PRD and write structured artifacts to .context/spec/requirements.json and .context/project-overview.md.