How do I install the Requirement Architect skill?

Run npx skillmds add majiayu000/requirement-architect in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Requirement Architect safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Requirement Architect?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Requirement Architect free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under CC-BY-SA-4.

Who published Requirement Architect?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Requirement Architect by majiayu000

Name: Requirement Architect
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

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: 

---name: requirement-architectdescription: 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--- # 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)  ## 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:** ``

Frequently asked questions