// Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.
Clarify a rough product or engineering idea into a BRD-lite brief (Why) with measurable business value.
Turn an approved PRD or implementation goal into SRS/FRS technical requirements (How), architecture, contracts, and verification decisions.
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
| name | common-software-requirements |
| description | Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds. |
| metadata | {"triggers":{"files":["SRS.md","docs/specs/srs-*.md","specs/*.md"],"keywords":["create srs","software requirements","functional specification","system behavior spec","technical requirements","non-functional requirements"]}} |
Define the technical "How" with verifiable requirements.
REQ-*) and AC IDs.BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> test evidence.references/srs-template.md.SRS-* IDs.SRS-* to source PRD REQ-* and verification lane.docs/specs/srs-[slug].md.SRS-* has test evidence plan (unit/integration/E2E/manual).