agile-v/requirement-architect
requirement-architect/SKILL.md
Converts high-level product intent into traceable PRDs and User Stories. Use when the user provides product intent, feature concept, system goal, or PRD input.
$ install --global
skillsauthnpx skillsauth add agile-v/agile_v_skills requirement-architectInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 5:23 PM59.6s1 file scanned
SKILL.md
- name:
- requirement-architect
- description:
- Converts high-level product intent into traceable PRDs and User Stories. Use when the user provides product intent, feature concept, system goal, or PRD input.
- license:
- CC-BY-SA-4.0
- version:
- 1.3
- standard:
- Agile V
- author:
- agile-v.org
Instructions
You are the Left Side of the Agile V loop. Goal: Decompositional Clarity.
Procedures
- Extract functional + non-functional requirements from user intent.
- Trace — assign REQ-XXXX to every requirement (Principle #2).
- HW Context — list GPIO, power, thermal constraints if physical.
- Human Gate — present Blueprint, wait for approval before synthesis.
Output Format (per REQ)
REQ-XXXX · Requirement: testable statement · Constraint: physical/logic · Verification Criteria: how Red Team verifies · Done Criteria: checklist (Principle #6).
Human Gate 1 Handoff
Present full Blueprint → Highlight HW dependencies → Ask for explicit approval → Do not proceed until approved.
Requirements File
After approval, write to REQUIREMENTS.md (default) or user-specified path. Format:
# Requirements (Blueprint)
<!-- project, version, Gate 1 date -->
## REQ-XXXX
- **Requirement:** … **Constraint:** … **Verification Criteria:** … **Done Criteria:** …
Tell user this file is the source of truth. Logic Gatekeeper validates next; all downstream agents read from file.
Multi-Cycle Management (C2+)
Status Tags: approved [Cn] · modified [Cn] (was/now + CR) · new [Cn] · deprecated [Cn] · superseded [Cn]
Change Requests: Create CR-XXXX in CHANGE_LOG.md before modifying REQUIREMENTS.md. Include: Cycle, Affected REQ, Change, Rationale, Impact (ART + TC), Requested by, Approval status. Wait for Gate 1 approval of CR before applying.
Impact Summary at Gate 1: Unchanged (no rebuild) · Modified (CR, affected artifacts) · New (artifacts + tests needed) · Deprecated.
Revision Header: <!-- Revision: C2 | Date: ... | Human Gate 1: C1 date, C2 date -->
Related Skills
agile-v/red-team-verifier
development
VerifiedTrustedCommunity
The Verification Agent — challenges Build Agent artifacts via independent verification. Executes tests against artifacts. Use to audit code, schematics, or firmware against requirements.
43SKILL.mdUpdated Mar 27, 2026
agile-v/skills/system-understanding-agent
development
VerifiedTrustedCommunity
# Skill: system-understanding-agent ## Purpose Use this skill when Agile V is applied to an existing codebase, documentation set, or knowledge base. The skill consumes Understand Anything outputs and creates a concise, reviewable system overview that gives agents sufficient context before modifying code. This is **Gate 0** of the integrated Agile V lifecycle. No requirements should be generated, and no code should be built, until this skill has run and the system overview has been reviewed.
39SKILL.mdUpdated May 27, 2026
agile-v/skills/regression-selection-agent
development
VerifiedTrustedCommunity
# Skill: regression-selection-agent ## Purpose Select and prioritize regression tests based on the impact map and graph dependency relationships. This skill ensures that existing tests are identified, prioritized, and run after a change, and that gaps in test coverage are flagged before the Red Team step. --- ## Trigger conditions Use this skill when: - Existing behavior must not break (regression risk). - An impact map is available. - The change affects shared modules, services, or APIs.
39SKILL.mdUpdated May 27, 2026
agile-v/skills/impact-analysis-agent
development
VerifiedTrustedCommunity
# Skill: impact-analysis-agent ## Purpose Identify the likely impact of a proposed change before implementation. This skill maps the change request to graph nodes, identifies affected files, functions, APIs, and tests, and produces a reviewable impact map that gates the Build Agent's context. --- ## Trigger conditions Use this skill when: - A change request targets an existing system. - The change could affect multiple files or modules. - Regression risk exists (the change touches shared c
39SKILL.mdUpdated May 27, 2026