skills.rest
thompson0012
thompson0012COMMUNITY
Explore all skills by this author →
WebsiteGitHub

requirements-writer

Generate a requirements document with user stories and acceptance criteria from a validated blueprint.

28|2|Updated Feb 5, 2026
Search Tags:#requirements#edge-cases#prd#user-stories#acceptance-criteria#engineering-hand-off
One-click install
npx skills add https://github.com/thompson0012/agents-stack --skill requirements-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-writer
Source: https://github.com/thompson0012/agents-stack/tree/main/templates/.agents/skills/greenfield-product/requirements-writer
Command: npx skills add https://github.com/thompson0012/agents-stack --skill requirements-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when a validated blueprint exists and you need actionable requirements, user stories, and acceptance criteria that become docs/reference/requirements.md.

Core Features & Use Cases

  • Turn validated blueprints into user stories, jobs to be done, and acceptance criteria.
  • Produce a complete PRD-style requirements document at docs/reference/requirements.md.
  • Clarify edge cases, non-goals, and open questions to hand off to engineering.

Quick Start

Provide a validated blueprint and run this skill to generate the requirements document at docs/reference/requirements.md.

Frequently Asked Questions about requirements-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a blueprint into user stories and acceptance criteria?▼

To turn a validated blueprint into user stories and acceptance criteria, provide the blueprint as input to generate a complete requirements document containing jobs to be done, edge cases, and non-goals.

What is the best way to generate a PRD for engineering hand-off?▼

Generating a PRD for engineering hand-off is best accomplished by transforming a validated blueprint into a structured requirements document featuring user stories, acceptance criteria, and open questions.

How do I define non-goals and edge cases for a software project scope?▼

Defining non-goals and edge cases for software project scope involves processing a validated blueprint to produce actionable requirements that explicitly clarify boundaries and open questions for engineering teams.

Can I draft complete product requirements without starting from scratch?▼

Drafting complete product requirements without starting from scratch is possible if you have a validated blueprint, which can be processed to automatically generate a PRD-style requirements document.

Where are generated product requirements stored when drafting a PRD?▼

Generated product requirements are stored as a markdown file at docs/reference/requirements.md, containing the full scope definition, user stories, and acceptance criteria for the project.

Does this requirements writer work without external dependencies?▼

This requirements writer operates without external dependencies, requiring only a validated blueprint as input to produce the complete requirements document for engineering teams.

Related Skills

Explore More Product & Management Skills→
mohamednegm0mohamednegm0

mvp

Guide founders through a three-stage MVP scope, build, and release framework.

Community
Intermediate
giovannimnzgiovannimnz

gsd-new-project

Initialize a new project by generating a planning scaffold with PROJECT.md, ROADMAP.md, REQUIREMENTS.md, and STATE.md.

Community
Advanced
dipandhali2021dipandhali2021

scrum-master

Plan sprint iterations and draft user stories with acceptance criteria.

Community
Advanced
samjhechtsamjhecht
4

writing-specifications

Generate implementation-ready technical specifications using the SPECIFICATION_TEMPLATE.md structure.

Community
Advanced