From deliverable
Drafts technical requirements (SRS) section by section, reading the existing BRD as input. Covers architecture, interfaces, data, NFRs, security, compliance, and rollout. Produces srs.md. Use when the user asks for an SRS, technical spec, architecture doc, engineering requirements, or "how should we build this."
How this skill is triggered — by the user, by Claude, or both
Slash command
/deliverable:deliverable-srsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Load on demand from the sibling `deliverable/` skill folder: `roles/*.md`, `templates/*.md`, `sub-agents/*.md`, `references/*.md`.
Load on demand from the sibling deliverable/ skill folder: roles/*.md, templates/*.md, sub-agents/*.md, references/*.md.
Draft software requirements based on an approved BRD. Covers architecture, interfaces, data, NFRs, security, compliance, and rollout — each section drafted with your approval.
Announce at start: "I'm using the deliverable-srs skill to draft an SRS based on the approved BRD."
NEVER draft the entire SRS in one shot. NEVER write multiple sections in a single turn. NEVER advance without user approval. NEVER write to disk without confirmation.Reads docs/requirements/brd.md on start. If no BRD exists, suggest running deliverable-brd first.
flowchart TD
P1[Architecture] --> P2[Interfaces & Data]
P2 --> P3[Non-functional]
P3 -->|auto-bump| P4[Security & Privacy]
P4 --> P5[Compliance]
P5 --> P6
P3 -->|no signals| P6[Rollout & Rollback]
P6 --> P7[SRS Sign-off]
P7 --> P8[Dual-voice SRS Review]
P8 --> DONE[Done → suggest red-team]
Interview using roles/tech-lead.md. Reference references/google-design-doc-patterns.md. Draft:
Interview using roles/tech-lead.md. Draft:
Interview using roles/tech-lead.md, roles/sre.md, roles/qa.md, roles/security-legal.md*. Draft:
*security-legal if auto-bump signals detected
Triggered when state.md has auto-bump signals. Interview using roles/security-legal.md. Draft:
Interview using roles/security-legal.md. Draft:
Interview using roles/sre.md. Draft:
Present full SRS. List all [ASSUMPTION] and [OPEN] items. Ask for sign-off.
Dispatch sub-agents/dual-voice-reviewer.md for independent second opinion on architecture and NFRs. Present findings.
| Section | greenfield | feature | internal |
|---|---|---|---|
| §integration | light | heavy | medium |
| §migration-compat | skip | required | required |
| §api-versioning | medium | medium | heavy |
| §deprecation | optional | required | required |
Same as deliverable-brd: Orient → Work → Present → Approve → Commit. One section at a time, no silent writes.
references/hyrum-law-checklist.md when reviewing interfaces."SRS complete. Ready for adversarial review? Say 'red-team this' to continue."
npx claudepluginhub canhta/deliverable --plugin deliverableProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.