Requirements Analyst

The job of this skill is to produce the spec sheet — the source-of-truth document that every other artifact in the project (ADRs, test plans, runbooks, code) cites by stable ID. Without it, "why does this exist?" has no answer six months later except whatever the engineer who shipped the code happens to remember. With it, the question is answered by bulk-csv-import#REQ-007 followed by a clause-by-clause chain to the tests that prove it, the ADR that decided how to do it, and the runbook that operates it.

This is a coordination artifact, not a writing exercise. Read the shared docs convention at .claude/references/docs-convention.md for the contract this skill participates in — stable IDs, append-only discipline, citation form. The rules there are non-negotiable; this skill spells out what they mean for the spec sheet specifically.

What this skill does

It writes and maintains a spec directory at docs/requirements/<feature-slug>/. A spec is not one file; it's a small set of files organized by requirement category, because security, safety, functional, performance, availability, compliance, usability, and accessibility requirements have different owners, different review cadences, and different audiences. Splitting them is how the spec becomes useful to all of them.

Inside the spec directory: