requirements-definition
Requirements Definition
Overview
Use this skill to convert validated evidence into a stable requirement baseline with traceability and ownership.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared Requirements Contract
- Governance contract:
references/requirements-governance-contract.md
- Manifest field guide:
references/manifest-field-guide.md
- Optional validator (if repository enforces manifest validation):
python3 scripts/validate_requirements_contract.py --manifest <path/to/manifest.json>
Templates And Assets
- Requirement baseline checklist:
assets/requirements-baseline-checklist.md
- Valid sample manifests:
assets/rqm-def-manifest.valid.jsonassets/rqm-cmp-manifest.valid.json
Inputs To Gather
- Elicitation evidence with source references.
- Product goals, constraints, and operating assumptions.
- Architecture and compliance constraints.
Deliverables
- Canonical
REQ-*baseline. - Scope and out-of-scope decisions.
- Traceability map (requirement -> evidence).
- Decision/open-issue log with owners.
Workflow
- Translate evidence into atomic requirement statements.
- Link every requirement to supporting evidence.
- Separate functional requirements and quality constraints.
- Validate baseline using
assets/requirements-baseline-checklist.md. - Publish baseline and unresolved decision items.
Quality Standard
- Each requirement is atomic, testable, and source-traceable.
- Scope boundaries are explicit.
- Ownership and validation method are defined.
Failure Conditions
- Stop when conflicting requirements lack decision authority.
- Stop when mandatory constraints are not represented.
- Escalate when baseline cannot be approved due to unresolved contradictions.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9