Menu
Generate testable EARS requirements and measurable acceptance criteria for an SDD feature.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Commit verified SDD changes and prepare a focused pull request.
Design an approved SDD feature with traceable components, interfaces, risks, and tests.
Implement approved SDD tasks test-first with focused verification and security checks.
Review a focused change for correctness, regressions, security, and maintainability.
Audit a focused scope for exploitable security flaws and prioritized remediation.
Define scoped custom steering for a verified project convention or domain.
| name | sdd-requirements |
| description | Generate testable EARS requirements and measurable acceptance criteria for an SDD feature. |
| disable-model-invocation | true |
sdd-init.sdd-status.The system SHALL ...WHEN ... THEN the system SHALL ...WHILE ... THE system SHALL ...WHERE ... THE system SHALL ...IF ... THEN the system SHALL ...sdd-validate-gap when existing code is in scope..spec/specs/{feature}/requirements.md. Request requirements approval only after the artifact is complete; never self-approve silently.Target renderers provide the planner route. When a native advisor is required, dispatch exactly one compact handoff with specialistDepth: 1; include only the goal, verified context, constraints, open decisions, and output contract. The specialist must not delegate again. Keep the handoff and returned summary at or below 2,048 estimated tokens. If the advisor or routed model is unavailable, record one fallback and continue in the parent without retrying or selecting a generic child. Where a native per-turn model override applies, execute in this turn.
Return the saved path, key scope decisions, validation evidence, and approval as the next action.
Read REFERENCE.md only for EARS examples, document structure, or the extended quality checklist.