requirements-spec-writer

To write a PRD and technical spec from a vague idea, the skill runs a focused interview to surface missing information, then generates structured requirements, acceptance criteria, and a phased implementation plan.

The best way to create user stories with measurable acceptance criteria is to input your feature brief and let the skill produce testable requirements, explicit out-of-scope items, and edge-case handling automatically.

To break down product features into phased implementation tasks, the skill converts stakeholder notes into developer-facing technical specifications and actionable implementation plans tailored for engineering teams.

Yes, you can generate API contracts and out-of-scope items from stakeholder notes; the skill highlights ambiguous or conflicting requirements and produces structured technical specifications with clear non-functional targets.

Yes, this requirements writing process handles edge cases for web and mobile platforms by producing testable requirements, measurable acceptance criteria, and explicit non-functional targets across both environments.