requirements-engineering

SKILL.md

Patterns for translating product vision into clear, actionable engineering specifications.

| Independent | Can be developed separately | No hard dependencies on other stories | | Negotiable | Details can be discussed | Not a contract, a conversation starter | | Valuable | Delivers user/business value | Answers "so what?" | | Estimable | Can be sized by the team | Clear enough to estimate | | Small | Fits in a sprint | 1-5 days of work typically |

| Testable | Has clear acceptance criteria | Know when it's done |

User stories, acceptance criteria, PRDs, and requirements documentation patterns. Use when translating product vision to engineering specs, writing user stories, or creating requirements documents. Source: yonatangross/orchestkit.

View raw