requirements-writer

To write structured acceptance criteria for a feature spec, use a guided conversation to transform rough PM notes into GIVEN/WHEN/THEN formats within a standardized requirements document. This process ensures all business rules and scope are captured clearly for engineering handoff.

The best way to turn rough product ideas into engineering requirements is through a guided conversation that extracts context and scope. It produces a finalized requirements.md file with YAML frontmatter and Markdown sections, enforcing strict PM boundaries to exclude architectural decisions.

Yes, you can generate a requirements document that strictly enforces PM lane governance. It actively excludes architectural decisions, estimates, and implementation specifics, ensuring only business rules, scope, and acceptance criteria are documented for the engineering team.

Yes, the requirements output follows a fixed schema for PM compliance. It generates a requirements.md file containing YAML frontmatter, structured Markdown sections, and standardized acceptance criteria formatting to ensure consistent engineering handoff.

Before starting feature scoping, prepare a rough feature prompt or PM notes. The guided conversation will use this initial input to extract the necessary context, scope, and open questions required to finalize the complete requirements specification.