Initial commit: antigravity-ipa-workflow
This commit is contained in:
96
skills/ipa-srd/SKILL.md
Normal file
96
skills/ipa-srd/SKILL.md
Normal file
@@ -0,0 +1,96 @@
|
||||
---
|
||||
name: ipa-srd
|
||||
description: Generate SRD.md only — the System Requirement Definition following IPA standard with 15 sections. Use when granular control over requirement generation is needed, when only the SRD needs to be regenerated without touching UI_SPEC, or when working as a Business Analyst generating structured requirements. Trigger phrases: "generate srd only", "create system requirement definition", "generate srd without ui spec".
|
||||
---
|
||||
|
||||
> TIP: Use ipa-spec instead to generate both SRD.md + UI_SPEC.md in one step.
|
||||
>
|
||||
> This skill is for granular control when you only need SRD.md.
|
||||
|
||||
## Overview
|
||||
|
||||
Generate System Requirement Definition (SRD) following IPA (Information-technology Promotion Agency, Japan) standard from raw requirements. Output: `docs/SRD.md`.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Only the SRD needs to be created or regenerated
|
||||
- Granular control is needed over requirement documentation
|
||||
- Iterating on requirements without changing UI spec
|
||||
- Acting as Business Analyst generating structured requirements
|
||||
|
||||
## Don't Use When
|
||||
|
||||
- Both SRD and UI_SPEC are needed (use ipa-spec)
|
||||
- Existing SRD needs only minor updates (edit directly)
|
||||
|
||||
## Input
|
||||
|
||||
Read from arguments, then `docs/requirements.md`, then `docs/PRD.md`, then ask user.
|
||||
|
||||
## Role
|
||||
|
||||
Business Analyst following IPA guidelines:
|
||||
- Requirement Definition (要件定義)
|
||||
- Ensure traceability: FR ↔ Screen ↔ Flow ↔ Entity
|
||||
|
||||
## Output: docs/SRD.md (15 Sections)
|
||||
|
||||
```markdown
|
||||
# System Requirement Definition (SRD)
|
||||
|
||||
## 1. System Name
|
||||
## 2. System Objectives
|
||||
## 3. User Roles (RBAC)
|
||||
| Role ID | Role Name | Description | Permissions |
|
||||
|
||||
## 4. Feature List
|
||||
| FR-ID | Feature Name | Description | Priority | Screens |
|
||||
|
||||
## 5. Screen List
|
||||
| S-ID | Screen Name | Description | Features |
|
||||
|
||||
## 6. Batch List
|
||||
| B-ID | Batch Name | Description | Schedule |
|
||||
|
||||
## 7. Report List
|
||||
| R-ID | Report Name | Description | Format |
|
||||
|
||||
## 8. Integration List (I/F)
|
||||
| IF-ID | Name | Type | Description |
|
||||
|
||||
## 9. Entity List & ER Diagram
|
||||
| E-ID | Entity Name | Description |
|
||||
|
||||
## 10. Screen Flow
|
||||
[Mermaid flowchart]
|
||||
|
||||
## 11. Main Business Flows
|
||||
## 12. Use Cases
|
||||
| UC-ID | Name | Actor | Precondition | Flow | Postcondition |
|
||||
|
||||
## 13. Non-Functional Requirements (NFR)
|
||||
## 14. Key Decisions
|
||||
| D-ID | Decision | Context | Alternatives | Chosen | Rationale |
|
||||
|
||||
## 15. IPA Checklist
|
||||
- [ ] All features covered
|
||||
- [ ] ID consistency (FR-xx, S-xx, E-xx, D-xx)
|
||||
- [ ] ERD + Screen Flow present
|
||||
- [ ] NFR defined
|
||||
- [ ] Key decisions documented
|
||||
- [ ] Acceptance criteria defined
|
||||
```
|
||||
|
||||
## Rules
|
||||
|
||||
- No fabrication: only document what is in requirements
|
||||
- Consistent IDs: FR-xx, S-xx, B-xx, R-xx, IF-xx, E-xx
|
||||
- Traceability: FR ↔ Screen ↔ Flow ↔ Entity must trace back
|
||||
|
||||
## After Generation
|
||||
|
||||
1. Save to `docs/SRD.md`
|
||||
2. Ask user to review
|
||||
3. Proceed to ipa-bd for Basic Design, or ipa-spec for SRD + UI_SPEC together
|
||||
|
||||
Does not implement code — only generates documentation.
|
||||
Reference in New Issue
Block a user