Requirements Document Analysis

Analyze an OpenSpec requirements spec (from openspec/specs/<capability>/spec.md, or a delta spec under openspec/changes/**/specs/) and produce three outputs:

1. Internal consistency — whether requirements contradict each other or the schema.
2. Implementation compliance — whether the implementation meets each requirement.
3. Test opportunities — concrete unit or acceptance tests that would verify requirements programmatically.

Input

• Requirements document: User specifies the path (e.g. openspec/specs/elasticsearch-security-role/spec.md) or the entity name/implementation path. Resolve to the spec.md under openspec/specs/<capability>/ (or the relevant delta spec path).
• Implementation: From the doc’s “Resource implementation” or “Data source implementation” line (e.g. internal/elasticsearch/security/role). Use that package for compliance and test analysis.

Workflow

0. OpenSpec structural validation (recommended when a shell is available)

Before deep analysis, run the OpenSpec CLI so the spec matches what CI enforces. This checks structure (e.g. ### Requirement: / #### Scenario: shape, SHALL / MUST in requirement bodies)—not semantic consistency or implementation compliance.