Menu
Generate EARS-compliant requirements
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
| name | aget-generate-requirement |
| description | Generate EARS-compliant requirements |
| archetype | spec-engineer |
| allowed-tools | ["Read","Glob"] |
Generate EARS-compliant requirements from stakeholder input or analysis. Ensures testability and proper formatting.
When this skill is invoked:
Understand the Need
Classify Requirement
Select EARS Template
Assign ID
Verify Testability
Ubiquitous:
The [system] SHALL [action].
Event-Driven:
WHEN [event], the [system] SHALL [action].
State-Driven:
WHILE [state], the [system] SHALL [action].
Conditional:
IF [condition], the [system] SHALL [action].
Combined:
WHEN [event] WHILE [state], IF [condition],
the [system] SHALL [action].
## Generated Requirement
### Input
**Need**: [Original description]
**Source**: [Who/What identified this need]
### Classification
| Attribute | Value |
|-----------|-------|
| Type | [Functional/NFR/Constraint] |
| Pattern | [Ubiquitous/Event/State/Conditional] |
| Priority | [Must/Should/May] |
### Requirement
**ID**: R-[XXX]-[NNN]
**Statement**:
> [EARS-formatted requirement]
### Testability
**Verifiable**: Yes
**Test Approach**: [How to verify]
**Acceptance Criteria**:
- [Criterion 1]
- [Criterion 2]
### Traceability
| Link | Reference |
|------|-----------|
| Source | [Need/User story] |
| Related | [Other requirements] |
---
### Clarifying Questions (if ambiguous)
1. [Question about unclear aspect]
R-[Domain]-[Number]
Examples:
- R-CLI-001 (CLI domain)
- R-SESSION-002 (Session domain)
- R-SKILL-003 (Skill domain)
Close a PROJECT_PLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECT_PLAN lifecycle.
Commit a selected candidate goal into a durable, governed Goal artifact. The D71-Strict singular committer of the propose-goals→create-goal verb pair (L1067/L1085). Two-tier (REQ-3): committed goals = a structured section in governance/GOALS.md; aspirational = agent-internal .aget/goals/aspirational.jsonl. Direct authoring of a committed-Goal section is PROHIBITED once this skill is invoked. Implements AGET_GOAL_SPEC v0.2.0 (CAP-GOAL-001..011).
Scaffold approved initiative manifests at planning/initiatives/INIT-*.md. Mirrors /aget-create-project STRICT (D71 Layer 2) — direct Write/Edit to planning/initiatives/ is PROHIBITED once this skill is invoked. Implements SOP_initiative.md (graduated procedure) + future AGET_INITIATIVE_SPEC. Consumes PROPOSAL_init_*.md substrate produced by /aget-propose-initiative.
Create lightweight initiative proposals (PROPOSAL_init_*.md) before full INIT-*.md scaffolding. Follows 'propose -> review -> approve -> create' governance pattern. Advisory enforcement. Implements AGET_INITIATIVE_SPEC v1.0.1 CAP-INIT-PROP-001..012.
Record principal authorization (GO) with Healthy Friction enforcement of the principle-triad (spec+verify-first, coherence-next, evidence-driven); release agent execution within authorized scope. Authorization-only — does not execute the authorized work.
Generate standalone narrative documents from session artifacts, optimized for a target consumption medium (NotebookLM, slides, memo, share-draft). Use when the user says "create briefing", "create a briefing for NotebookLM", "make this listenable", "summarize session for [medium]", "prepare a listen", "brief me on [topic]", or "create a summary I can share".