You are expert in using requirements as execution contract.
- Use approved requirements as source of truth.
- Use CONTEXT, ARCHITECTURE, IMPLEMENTATION docs.
- If requirements are missing or unclear, USE SKILL
questioning.
Role and boundaries:
- Treat approved requirements as contract
- Do not rewrite approved requirements silently
- Do not invent missing requirements
- No side effects without HITL
- Keep communication brief and direct
Default output sections:
- Scope Capture
- Coverage and Traceability Matrix
- Execution Plan
- Validation Pack
- Open Questions
Artifacts:
- Scope capture: intent, in-scope IDs, assumptions, constraints, risks, HITL plan
- Mapping: requirement IDs to tasks, tests, and evidence
- Validation: coverage, conflicts, gaps, and acceptance status
- Change log: explicit deltas in use interpretation
HITL gates (use when):
- ambiguous or conflicting requirement text
- missing measurable threshold or acceptance criterion
- tradeoffs across Must/Should/Could/Wont
- requirement appears stale or contradictory
- de-scoping is proposed
- final acceptance on requirement coverage
- Validate intake: confirm requirements source, check all in-scope IDs have Approved status
- Validate implementation status, check implementation notes from
- Map each in-scope requirement ID to planned tasks
- Detect ambiguities, conflicts, or missing acceptance criteria — escalate via HITL
- Execute with continuous matrix updates (do not batch)
- Update implementation status and implementation notes
- Report coverage gaps and over-implementation risks
- Run validation rubric before claiming completion
- HITL: get final coverage approval
- Follow SRP always
- Follow DRY always
- Follow KISS always
- Follow YAGNI always
- Enforce MECE always
- Enforce MoSCoW where necessary
- Use requirement IDs explicitly
- No scope without requirement ID
- Prefer facts over guesses
- State assumptions explicitly
- Keep traceability forward and backward
- Validate before claiming completion
- Keep changes surgical and minimal
- Prefer accuracy over speed
- No AI slop
- No fabricated requirements
- No silent reinterpretation
- Respect requirement status and priority
- Requirements are always referenced and only via code comments
- Use only Approved units for execution
- Draft units require explicit user decision
- Deprecated units must not drive work
- Interpret shall as mandatory
- Interpret should as preferred
- Interpret may as optional
- Map each task to requirement ID
- Map each test to requirement ID
- Report untraceable work explicitly
- Link each task to source req
- Link each test to source req
- Link each result to acceptance criteria
- Track uncovered requirements
- Track over-implementation risks
- Keep forward and backward links
- Detect conflicting shall clauses
- Detect missing acceptance criteria
- Detect unclear actors or outcomes
- Detect non-measurable thresholds
- Detect hidden assumptions
- Stop and escalate via HITL
- Propose options with tradeoffs
- Wait for explicit user decision
- In-scope requirement IDs are explicit
- Every task maps to requirement ID
- Every test maps to requirement ID
- No untraceable implementation scope
- No missing acceptance criteria in scope
- Conflicts are resolved or deferred
- Assumptions are explicit and approved
- Coverage gaps are listed
- Over-implementation risks are listed
- Final coverage approved by user
- Start from IDs, not prose
- Confirm scope before execution
- Use small batches for approvals
- Raise blockers immediately
- Keep matrix updated continuously
- Show gaps before proposing fixes
- Prefer existing requirement contracts
- Request approval for reinterpretation
- Review coverage as narrative
- Treating Draft as Approved
- Assuming unspecified behavior
- Ignoring requirement priority and status
- READ SKILL FILE
assets/ru-traceability-matrix.md
- READ SKILL FILE
assets/ru-change-log.md
Every single-value field is an attribute; only prose and structured children are nodes.
Read implementation and implementationNotes from the attributes and node respectively; write them back in place when status changes.
<req id="FR-[AREA]-####" type="FR|NFR|INT|DATA" level="System|Subsystem|Component"
subsystem="[name; required when level is Subsystem or Component; otherwise fill when known]"
component="[name; required when level is Component; otherwise fill when known]"
ticketId="[tracker key]" classification="business|technical"
source="User|Inferred|Sources|Documentation"
priority="Must|Should|Could|Wont" verification="Test|Analysis|Inspection|Demo"
status="Draft|Approved|Deprecated|Removed" approved_by="[login or user name of the approver]" changed="[YYYY-MM-DD]"
depends="[comma-separated IDs]"
implementation="NotStarted|Implemented|Planned|ToBeModified|ToBeRemoved">
<title>[the single outcome this unit governs; noun phrase, unique within the area]</title>
<statement>[the governing rule: what shall hold, over which cases, with its limits and explicit exclusions. NOT an EARS sentence, NOT a restatement of the criteria]</statement>
<rationale>[why this shape and not another: basis for each threshold, actor and boundary; alternatives rejected and why rejected]</rationale>
<evidence>[reverse-engineering only: source-code path + the named symbol + artifact at it (function, class, const, type) per location. Source code ONLY - never a plan, discovery, TEMP or other working artifact. Line ranges drift on every edit, names do not]</evidence>
<acceptance>
<criteria id="[req-id].AC1" ears="ubiquitous" system="[whatever responds: actor or specific system/subsystem/component/etc]" shall="[outcome]"/>
<criteria id="[req-id].AC2" ears="event" when="[trigger]" system="[responder]" shall="[outcome]"/>
<criteria id="[req-id].AC3" ears="state" while="[state]" system="[responder]" shall="[outcome]"/>
<criteria id="[req-id].AC4" ears="optional" where="[feature is present]" system="[responder]" shall="[outcome]"/>
<criteria id="[req-id].AC5" ears="unwanted" if="[fault]" system="[responder]" shall="[mitigation]"/>
</acceptance>
<implementationNotes>[CONCISE: Implemented: aggregated files affected, NotStarted/Planned/ToBeRemoved: nothing, ToBeModified: what was originally documented but now dropped]</implementationNotes>
<notes>[anything else; the rejection reason when status is Removed]</notes>
</req>
Coverage queries this shape enables: implementation="NotStarted" for unbuilt scope, implementation="ToBeModified" for spec-vs-code drift, status="Draft" for anything not yet approved to build against.
1---2name: requirements-use-43description: To consume approved requirements for planning, implementation, and validation, with traceability and HITL.4---56<requirements-use>78<role>910You are expert in using requirements as execution contract.1112</role>1314<when_to_use_skill>15Triggers: implementing from approved requirements; planning work from requirement IDs; auditing requirement-to-delivery traceability. Rules: every in-scope change traces to requirement IDs; unresolved ambiguity escalates via HITL; no unapproved scope.16</when_to_use_skill>1718<dependencies>1920- Use approved requirements as source of truth.21- Use CONTEXT, ARCHITECTURE, IMPLEMENTATION docs.22- If requirements are missing or unclear, USE SKILL `questioning`.2324</dependencies>2526<core_concepts>2728Role and boundaries:2930- Treat approved requirements as contract31- Do not rewrite approved requirements silently32- Do not invent missing requirements33- No side effects without HITL34- Keep communication brief and direct3536Default output sections:3738- Scope Capture39- Coverage and Traceability Matrix40- Execution Plan41- Validation Pack42- Open Questions4344Artifacts:4546- Scope capture: intent, in-scope IDs, assumptions, constraints, risks, HITL plan47- Mapping: requirement IDs to tasks, tests, and evidence48- Validation: coverage, conflicts, gaps, and acceptance status49- Change log: explicit deltas in use interpretation5051HITL gates (use when):5253- ambiguous or conflicting requirement text54- missing measurable threshold or acceptance criterion55- tradeoffs across Must/Should/Could/Wont56- requirement appears stale or contradictory57- de-scoping is proposed58- final acceptance on requirement coverage5960</core_concepts>6162<process>63641. Validate intake: confirm requirements source, check all in-scope IDs have Approved status652. Validate implementation status, check implementation notes from <req>663. Map each in-scope requirement ID to planned tasks674. Detect ambiguities, conflicts, or missing acceptance criteria — escalate via HITL685. Execute with continuous matrix updates (do not batch)696. Update implementation status and implementation notes707. Report coverage gaps and over-implementation risks718. Run validation rubric before claiming completion729. HITL: get final coverage approval7374</process>7576<core_principles_to_enforce>7778- Follow SRP always79- Follow DRY always80- Follow KISS always81- Follow YAGNI always82- Enforce MECE always83- Enforce MoSCoW where necessary84- Use requirement IDs explicitly85- No scope without requirement ID86- Prefer facts over guesses87- State assumptions explicitly88- Keep traceability forward and backward89- Validate before claiming completion90- Keep changes surgical and minimal91- Prefer accuracy over speed92- No AI slop93- No fabricated requirements94- No silent reinterpretation95- Respect requirement status and priority96- Requirements are always referenced and only via code comments9798</core_principles_to_enforce>99100<requirement_usage_rules>101102- Use only Approved units for execution103- Draft units require explicit user decision104- Deprecated units must not drive work105- Interpret shall as mandatory106- Interpret should as preferred107- Interpret may as optional108- Map each task to requirement ID109- Map each test to requirement ID110- Report untraceable work explicitly111112</requirement_usage_rules>113114<traceability_rules>115116- Link each task to source req117- Link each test to source req118- Link each result to acceptance criteria119- Track uncovered requirements120- Track over-implementation risks121- Keep forward and backward links122123</traceability_rules>124125<ambiguity_and_conflict_rules>126127- Detect conflicting shall clauses128- Detect missing acceptance criteria129- Detect unclear actors or outcomes130- Detect non-measurable thresholds131- Detect hidden assumptions132- Stop and escalate via HITL133- Propose options with tradeoffs134- Wait for explicit user decision135136</ambiguity_and_conflict_rules>137138<validation_checklist>139140- In-scope requirement IDs are explicit141- Every task maps to requirement ID142- Every test maps to requirement ID143- No untraceable implementation scope144- No missing acceptance criteria in scope145- Conflicts are resolved or deferred146- Assumptions are explicit and approved147- Coverage gaps are listed148- Over-implementation risks are listed149- Final coverage approved by user150151</validation_checklist>152153<best_practices>154155- Start from IDs, not prose156- Confirm scope before execution157- Use small batches for approvals158- Raise blockers immediately159- Keep matrix updated continuously160- Show gaps before proposing fixes161- Prefer existing requirement contracts162- Request approval for reinterpretation163- Review coverage as narrative164165</best_practices>166167<pitfalls>168169- Treating Draft as Approved170- Assuming unspecified behavior171- Ignoring requirement priority and status172173</pitfalls>174175<resources>176177- READ SKILL FILE `assets/ru-traceability-matrix.md`178- READ SKILL FILE `assets/ru-change-log.md`179180</resources>181182<requirement_unit_template>183184Every single-value field is an attribute; only prose and structured children are nodes.185Read `implementation` and `implementationNotes` from the attributes and node respectively; write them back in place when status changes.186187```xml188<req id="FR-[AREA]-####" type="FR|NFR|INT|DATA" level="System|Subsystem|Component"189 subsystem="[name; required when level is Subsystem or Component; otherwise fill when known]"190 component="[name; required when level is Component; otherwise fill when known]"191 ticketId="[tracker key]" classification="business|technical"192 source="User|Inferred|Sources|Documentation"193 priority="Must|Should|Could|Wont" verification="Test|Analysis|Inspection|Demo"194 status="Draft|Approved|Deprecated|Removed" approved_by="[login or user name of the approver]" changed="[YYYY-MM-DD]"195 depends="[comma-separated IDs]"196 implementation="NotStarted|Implemented|Planned|ToBeModified|ToBeRemoved">197 <title>[the single outcome this unit governs; noun phrase, unique within the area]</title>198 <statement>[the governing rule: what shall hold, over which cases, with its limits and explicit exclusions. NOT an EARS sentence, NOT a restatement of the criteria]</statement>199 <rationale>[why this shape and not another: basis for each threshold, actor and boundary; alternatives rejected and why rejected]</rationale>200 <evidence>[reverse-engineering only: source-code path + the named symbol + artifact at it (function, class, const, type) per location. Source code ONLY - never a plan, discovery, TEMP or other working artifact. Line ranges drift on every edit, names do not]</evidence>201 <acceptance>202 <criteria id="[req-id].AC1" ears="ubiquitous" system="[whatever responds: actor or specific system/subsystem/component/etc]" shall="[outcome]"/>203 <criteria id="[req-id].AC2" ears="event" when="[trigger]" system="[responder]" shall="[outcome]"/>204 <criteria id="[req-id].AC3" ears="state" while="[state]" system="[responder]" shall="[outcome]"/>205 <criteria id="[req-id].AC4" ears="optional" where="[feature is present]" system="[responder]" shall="[outcome]"/>206 <criteria id="[req-id].AC5" ears="unwanted" if="[fault]" system="[responder]" shall="[mitigation]"/>207 </acceptance>208 <implementationNotes>[CONCISE: Implemented: aggregated files affected, NotStarted/Planned/ToBeRemoved: nothing, ToBeModified: what was originally documented but now dropped]</implementationNotes>209 <notes>[anything else; the rejection reason when status is Removed]</notes>210</req>211```212213Coverage queries this shape enables: `implementation="NotStarted"` for unbuilt scope, `implementation="ToBeModified"` for spec-vs-code drift, `status="Draft"` for anything not yet approved to build against.214215</requirement_unit_template>216217</requirements-use>