requirement-architect

$npx mdskill add Agile-V/agile_v_skills/requirement-architect

Converts product intent into traceable PRDs and User Stories

  • Extracts functional and non-functional requirements from user intent.
  • Deploys tools for requirement analysis and dependency tracking.
  • Decides on constraints based on physical and logical considerations.
  • Delivers a blueprint for review, ensuring alignment with project goals.

SKILL.md

.github/skills/requirement-architectView on GitHub ↗
---
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
metadata:
  version: "1.3"
  standard: "Agile V"
  author: agile-v.org
  sections_index:
    - Procedures & Output Format
    - Human Gate 1 Handoff
    - Requirements File Convention
    - Multi-Cycle Management
---

# Instructions

You are the **Left Side** of the Agile V loop. Goal: **Decompositional Clarity**.

## Procedures
1. **Extract** functional + non-functional requirements from user intent.
2. **Trace** — assign REQ-XXXX to every requirement (Principle #2).
3. **HW Context** — list GPIO, power, thermal constraints if physical.
4. **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:
```markdown
# 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.

## Traceability Lineage

Every REQ-XXXX must include one of:
- A reference to a discovery artifact (OBS-XXXX, INS-XXXX, HYP-XXXX, or EXP-XXXX from discovery-analyst), OR
- A `Stakeholder Directive: Yes` field with the stakeholder name and date

If neither is present, halt and return to Discovery phase. Do not create REQs from ambiguous chat alone.

## 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 -->`

More from Agile-V/agile_v_skills

SkillDescription
agile-v-behavioralAnti-pattern prevention guidelines for Agile V agents. Prevents common LLM coding mistakes while maintaining Agile V traceability. Use when implementing requirements to avoid overcomplication, silent assumptions, scope creep, and verification failures.
agile-v-complianceRisk management, CAPA protocol, human gate approval records, AI agent security controls, and periodic revalidation. Load when running gates, handling CAPAs, or auditing compliance and security posture.
agile-v-control-matrixDefines and checks the Agile-V control matrix for agentic tasks, skills, model use, tools, logs, rights, Human Gates, tests, costs, rollback, and owners. Load when creating, reviewing, or enforcing `.agile-v/CONTROL_MATRIX.yaml` or runtime governance for agentic execution.
agile-v-coreFoundational values, directives, and context engineering rules for all Agile V agents. Load first in every Agile V session.
agile-v-lifecycleMulti-cycle iteration management, document versioning, change requests, re-entry points, archival, and impact analysis. Load when starting a new cycle (C2+), processing change requests, or managing cross-cycle traceability.
agile-v-pipelineOrchestration pipeline, wave execution, handoff protocols, and checkpoint types for the Agile V 5-stage workflow. Load when orchestrating multi-agent pipelines or managing stage transitions.
agile-v-product-ownerREQ-aware Product Owner for backlog and sprint management with full traceability. Use for sprint planning, backlog prioritization, or converting REQs to INVEST stories.
agile-v-quality-gatesQuality validation gates for Agile V agents. Adds interface validation, test quality checks, data type awareness, and time allocation guidance to prevent common failure patterns identified in comprehensive testing.
build-agentGenerates code, firmware, HDL, or other technical artifacts strictly derived from approved requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-approved requirements.
build-agent-dartDart/Flutter build agent for mobile apps, Flutter widgets, and Dart packages. Extends build-agent with Dart-specific conventions. Use when building Flutter apps, Dart packages, or mobile (iOS/Android) features.