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.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/common/common-software-requirements/SKILL.mdDefine the technical "How" with verifiable requirements.
Confirm linked PRD requirements (REQ-*) and AC IDs.
Preserve trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> test evidence.
Delivery Mode: Carry delivery_mode separately from snc_tier. brief (approved low-risk, nonsensitive work with outcome, scope fence, owner, observable criteria, approval reference, verification lane) uses the ticket/session record and writes no SRS. standard writes this focused SRS only when technical decisions or contracts need an explicit design; extended adds risk-triggered contracts, migration, capacity, or failure analysis. Missing mode is a routing decision from approved evidence and risk, never automatic permission to skip design.
Conditional Sections: Fill the core; add an extension only when its trigger applies. Omit irrelevant sections instead of writing "none" paragraphs; omitting an applicable extension is an owned blocker.
Missing behavioral acceptance criteria, accountable owner, consequential design approval, or verification prerequisites route EVERY affected slice back to requirements/planning regardless of new or existing scope. Bounded low-risk equivalence (approved ticket with behavioral AC, owner, scope fence, approval, verification lane) may replace separate SRS files and formal IDs, but never waives behavioral prerequisites; do not infer product scope from code.
Sensitive changes require technical design and explicit human/governance approval per requirements modeling §1; low-risk equivalence never removes that floor.
Define functional flows: trigger, inputs, validations, outputs, errors.
For complex flows, use one actor, one goal, one session; split normal, alternate, and exception courses.
Define interface contracts: API, events, storage, external integrations.
Define NFRs: numeric thresholds where appropriate (latency, availability, scalability) and categorical verifiable invariants where appropriate (security, access control, integrity); never fabricate numbers.
Define constraints: migration, compatibility, compliance, rollout.
Consume the canonical conflict, requirement-quality-versus-need-validation, and temporary-transition distinctions in shared requirements modeling. Keep technical migration/rollback realization in SRS; do not duplicate the shared business-analysis rules.
references/srs-template.md.[slug] from the source docs/prd/prd-[slug].md to maintain filename-level traceability.SRS-* IDs, linking source REQ-*/AC-*, behavior, failure/fallback, NFR or security impact, and verification.feature_status, requirement trace, completed/missing evidence, decision needed, and recommended next workflow; the human document links the persisted run record.docs/srs/srs-[slug].md.HoangNguyen0403/agent-skills-standard
11c8bd1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.