skills/ HoangNguyen0403/agent-skills-standard

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.

0
Installs
—
Rating
—
Success rate
6
Files scanned
Scan passedbackend
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

6 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 ff059e42f11612b4… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

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.
  • Block or route back to PRD (plan-feature) when REQ-* or AC-* inputs are missing; do not infer product scope from code.
  • 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 source docs/prd/prd-[slug].md to maintain filename-level traceability.
  • Write one requirement card per statement with stable SRS-* IDs.
  • Map each SRS-* to source PRD REQ-* and verification lane.
  • Map every technical behavior to PRD ACs, test lane, and evidence target.
  • Include statement, priority, status, input/output/error behavior, NFR impact, measurement method, and evidence target.
  • Add outcome report: feature_status, requirement trace, completed/missing evidence, decision needed, and recommended next workflow.
  • 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 implementation handoff without mapped PRD AC IDs and test lanes.
  • No happy-path-only flow for complex user/system interactions.

References

Files

6
15.6 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from HoangNguyen0403/agent-skills-standard8

android-agp-upgrade

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

Scan passed 0
android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec

Scan passed 0
android-background-work

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

Scan passed 0
android-compose

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

Scan passed 0
android-compose-migration

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

Scan passed 0
android-concurrency

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci

Scan passed 0
android-deployment

Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.

Scan passed 0
android-design-system

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

Scan passed 0

Related backend skillsscan passed