メニュー
Skill for requirement analysis and PRD writing — stakeholder identification, user story mapping, acceptance criteria, PRD structure, and risk analysis.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Planning Mode skill for guided execution of large tasks. Provides structured task decomposition, user confirmation, per-task verification, retry logic, and quality summary.
Git 工作流 — 版本控制、提交规范、分支管理、.gitignore 治理
Structured bug diagnosis and repair workflow using the 5-Whys root cause analysis method. Ensures fixes include tests, documentation, and knowledge capture.
Generates structured documents including architecture diagrams (Mermaid), usage manuals, progress reports, and API documentation from code analysis.
Extracts reusable patterns and lessons from execution history and project experience. Generates structured knowledge entries for the knowledge base.
Evaluates project progress by analyzing workspace structure, code completeness, and comparing against planned milestones. Outputs structured progress reports.
SOC 職業分類に基づく
| 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. |
Guides the SuperAgent through the full requirement engineering lifecycle: from raw feature requests to well-structured PRDs with testable acceptance criteria.
| 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 |
Epic (large feature)
├── Feature (deliverable capability)
│ ├── User Story (user-facing behavior)
│ │ ├── Acceptance Criteria (Given-When-Then)
│ │ └── Technical Tasks
│ └── User Story
└── Feature
└── User Story
As a [persona], I want to [action/goal], so that [benefit/value].
Given [precondition/context],
When [action/trigger],
Then [expected outcome].
Rules:
Every PRD follows this structure (sections may be shortened for smaller features but never omitted):
| Bad | Good |
|---|---|
| "The system should be fast" | "API response time < 200ms at p95 under 1000 concurrent users" |
| "Handle errors gracefully" | "On validation error, return HTTP 400 with error code, field name, and message" |
| "should" | "must" (required) or "may" (optional) |
| "etc." | List all items explicitly |
| "appropriate" | Define what is appropriate |
| Category | Key Questions |
|---|---|
| Technical | Technically feasible? Do we have the skills? |
| Integration | External system dependencies? API stability? |
| Data | Data quality issues? Migration risks? |
| Performance | Can the system handle expected load? |
| Security | New attack surfaces? Compliance implications? |
| Schedule | Achievable in target timeline? |
| Probability / Impact | Low Impact | Medium Impact | High Impact |
|---|---|---|---|
| High Probability | Medium | High | Critical |
| Medium Probability | Low | Medium | High |
| Low Probability | Negligible | Low | Medium |