Common Software Requirements
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.
Install
$ agentstack add skill-hoangnguyen0403-agent-skills-standard-common-software-requirements ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hoangnguyen0403-agent-skills-standard-common-software-requirements) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Software Requirements Expert
Priority: P0 (CRITICAL)
Define the technical "How" with verifiable requirements.
1. SRS/FRS Discovery
- Confirm linked PRD requirements (
REQ-*) and AC IDs. - Preserve trace:
BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> test evidence. - 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 NFR thresholds: latency, availability, security, scalability.
- Define constraints: migration, compatibility, compliance, rollout.
2. Drafting Workflow
- Load
references/srs-template.md. - Slug Alignment: Use the same
[slug]from the sourcedocs/prd/prd-[slug].mdto maintain filename-level traceability. - Write one requirement card per statement with stable
SRS-*IDs. - Map each
SRS-*to source PRDREQ-*and verification lane. - Include statement, priority, status, input/output/error behavior, NFR impact, measurement method, and evidence target.
- Write to
docs/srs/srs-[slug].md.
3. Verification Mapping
- Each
SRS-*has test evidence plan (unit/integration/E2E/manual). - Failure modes and fallback behavior are explicit.
- Permissions and privacy controls mapped to requirements.
- Measurement method exists for each NFR.
Anti-Patterns
- No mixed requirements and implementation tasks in same statement.
- No NFR claims without numeric threshold.
- No interface contract without input/output/error schema.
- No requirement without trace link to source and verification.
- No happy-path-only flow for complex user/system interactions.
References
- [SRS Template](references/srs-template.md)
- [FRS Checklist](references/frs-checklist.md)
- [Requirements Baseline](references/standards-baseline.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: HoangNguyen0403
- Source: HoangNguyen0403/agent-skills-standard
- License: Apache-2.0
- Homepage: https://www.npmjs.com/package/agent-skills-standard
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.