Requirements Definition

Use ASD-STE100 Simplified Technical English when you ask questions or write output files.

Turn shared understanding into a validated Product Requirements Document. This skill can follow clarify, but clarification is optional when the user already knows what they want.

The skill makes no production-code changes and no commits. It reads the repository only to establish current behavior and constraints.

Input contract

Resolve the input before writing requirements.

A validated context brief exists

1. Read it fully.
2. Require artifact: context-brief and status: validated in its frontmatter. If it is still a draft, stop and offer to resume clarify.
3. Preserve its confirmed problem, desired outcome, scope, constraints, provenance, and unresolved questions. Do not silently reopen settled context.
4. Record the SHA-256 hash of the exact context-brief file in the PRD frontmatter so later stages can detect stale context.
5. Re-inspect repository facts that requirements depend on. If material repository drift contradicts the brief, show the evidence and ask before continuing.