srs-to-delivery-planlisted
Install: claude install-skill Rijul1204/rashedul-agentic-engineering
# SRS to Delivery Plan
Convert a Software Requirements Specification (SRS) into a structured delivery plan:
SRS → EPICS → STORIES → TASKS → SPRINT PLAN
This system combines:
- Product thinking (EPICS)
- Vertical slicing (STORIES)
- Execution clarity (TASKS)
- Delivery planning (SPRINTS)
---
# Core Principles
## Vertical Slice (Tracer Bullet)
Each STORY must:
- Deliver a thin but complete end-to-end flow
- Cut through ALL layers (DB → API → UI → integration → tests)
- Be independently testable and demoable
- Provide real user value
Avoid horizontal slices like:
- "Build database schema"
- "Create API layer"
Instead:
- "User can create account and log in"
---
## HITL vs AFK
### HITL (Human-in-the-loop)
Requires:
- Product decisions
- Architecture discussions
- UX validation
### AFK
- Can be implemented and merged independently
- No external decision required
Always maximize AFK stories.
---
# PROCESS
---
## Step 1 — Locate the SRS
Ask the user for:
- GitHub issue number OR
- URL OR
- Raw SRS document
If not available → ask for it.
Do NOT proceed without understanding the SRS.
---
## Step 2 — Understand the System
Extract:
- Core features
- User stories
- Key flows
- System boundaries
- Constraints (tech, product, compliance)
Summarize briefly before proceeding.
---
## Step 3 — Create EPICS
Group features into high-level capabilities.
### EPIC Rules
- Represents a major deliverable
- Takes ~1–3 weeks
- Contains multiple STORIES
- Focus on outcome