| name | requirement-engineering |
| description | Skill for requirement analysis and PRD writing — stakeholder identification, user story mapping, acceptance criteria, PRD structure, and risk analysis. |
| stage | planning |
| type | delivery-skill |
| version | 3.0 |
| category | delivery |
| scope | platform |
| tags | ["methodology","planning","requirements","prd"] |
| note | Merged from prd-writing + requirement-analysis. Covers the full requirement engineering lifecycle. |
Requirement Engineering Skill
Purpose
Guides the SuperAgent through the full requirement engineering lifecycle: from raw feature requests to well-structured PRDs with testable acceptance criteria.
Phase 1: Stakeholder & Context Analysis
Stakeholder Identification
- Direct stakeholders: requester, end users, dev team, QA, ops/support
- Indirect stakeholders: dependent teams, downstream services, compliance/regulatory
- Map concerns to priorities:
| Stakeholder | Concern | Priority |
|---|
| End User | Usability, performance | High |
| Product Owner | Business value, timeline | High |
| Dev Team | Feasibility, maintainability | Medium |
| QA Team | Testability, acceptance criteria | Medium |
| Ops Team | Deployability, observability | Medium |
| Security Team | Security, compliance | High |
- RACI matrix (for complex features): Responsible / Accountable / Consulted / Informed
Phase 2: User Story Mapping
Story Hierarchy
Epic (large feature)
├── Feature (deliverable capability)
│ ├── User Story (user-facing behavior)
│ │ ├── Acceptance Criteria (Given-When-Then)
│ │ └── Technical Tasks
│ └── User Story
└── Feature
└── User Story
User Story Format
As a [persona], I want to [action/goal], so that [benefit/value].
INVEST Criteria
- Independent: deliverable on its own
- Negotiable: details refined during development
- Valuable: delivers user or business value
- Estimable: team can estimate effort
- Small: completable within one sprint
- Testable: clear criteria to verify
Acceptance Criteria (Given-When-Then)
Given [precondition/context],
When [action/trigger],
Then [expected outcome].
Rules:
