Requirements Engineering

This skill turns the messy, iterative work of figuring out what to build into a durable, queryable artifact set. The goal is a living requirements repository: every requirement is atomic, uniquely identified, verifiable, and traceable to the need it came from and the decisions that shaped it. Nothing is captured as prose that should be captured as structure.

The work is fundamentally iterative and conversational. You are not filling in a form once. You interview the human in focused batches, write artifacts as you go, and resume from wherever the repository currently stands the next time. Treat the repository — not the chat — as the source of truth.

The artifact set

Everything lives in a requirements/ working tree (create it in the user's folder if it doesn't exist; adapt to an existing layout if one is already there):