requirement-architect

Installation
SKILL.md

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. Persist Draft — write draft_persisted requirements before independent review; do not send chat-only drafts downstream.
  5. Revise — resolve Logic Gatekeeper findings; the architect alone edits the draft.
  6. Human Gate — present revisions and findings; on approval create a frozen baseline 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.

Installs
1
GitHub Stars
54
First Seen
2 days ago
requirement-architect — agile-v/agile_v_skills