How do I install the Analyze Requirements skill?

Run npx skillmds add vukhanhtruong/analyze-requirements 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 Analyze Requirements safe to use?

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

Which AI agents work with Analyze Requirements?

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 Analyze Requirements free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Analyze Requirements?

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

Analyze Requirements by vukhanhtruong

Name: Analyze Requirements
Rating: 4.5 (4 reviews)
Author: vukhanhtruong

Analyze Requirements

Create or update professional architecture documentation through a structured interview, live research, and code scanning. Use when the user asks for architecture docs, system documentation, an architecture review doc, C4 diagrams, ADRs, a threat model, or to document an existing codebase.

vukhanhtruong 473ce93 114 files · 585.8 KB Updated Sep 10, 2026

File contents

analyze-requirements

Produce provenance-tagged architecture documentation with interactive diagrams, served on localhost for review.

Hard rules

Every fact carries provenance: observed | stated | researched (with source) | proposed. A claim nobody verified must never render like one that was.
One home per fact — diagrams own topology, tables own properties, prose owns neither.
Unknowns render as honest absences (Not applicable — <reason>, not estimated, Not provided) — never placeholders, never [TODO], never 0.
Validation blocks rendering: node scripts/validate.mjs must exit 0 before the viewer is generated.
mattpocock files (CONTEXT.md, CONTEXT-MAP.md, docs/adr/) are written into their existing formats — never restructured. Invoke the domain-modeling skill for term work.

Flow

Detect mode: target has source code → brownfield, else greenfield. State the detection and let the user override.
Scan (brownfield): index_repository if needed, then get_architecture — clusters seed §6 Core Components. Read manage_adr if present; never write it.
Interview: follow references/interview.md. Detect project type per references/project-types.md.
Research: run workflows/research.js per references/research.md. Surface dropped items before writing.
Write: model first (references/likec4.md), then ARCHITECTURE.md and companions (references/writing.md).
Validate: export the model with node scripts/likec4-export.mjs --dir ... --out ..., then node scripts/validate.mjs --arch ... --model ... (add --mode brownfield --clusters ... when applicable). Fix findings; re-run until clean.
Render + serve: follow references/viewer.md; report the URL.

Dependency

Node ≥ 20 with npm (npx likec4). State this upfront; without it, stop before step 5.

---name: analyze-requirementsdescription: Create or update professional architecture documentation through a structured interview, live research, and code scanning. Use when the user asks for architecture docs, system documentation, an architecture review doc, C4 diagrams, ADRs, a threat model, or to document an existing codebase.---# analyze-requirementsProduce provenance-tagged architecture documentation with interactive diagrams,served on localhost for review.## Hard rules1. Every fact carries provenance: `observed` | `stated` | `researched` (with source) | `proposed`. A claim nobody verified must never render like one that was.2. One home per fact — diagrams own topology, tables own properties, prose owns neither.3. Unknowns render as honest absences (`Not applicable — <reason>`, `not estimated`, `Not provided`) — never placeholders, never `[TODO]`, never `0`.4. Validation blocks rendering: `node scripts/validate.mjs` must exit 0 before the viewer is generated.5. mattpocock files (`CONTEXT.md`, `CONTEXT-MAP.md`, `docs/adr/`) are written into their existing formats — never restructured. Invoke the `domain-modeling` skill for term work.## Flow1. **Detect mode**: target has source code → brownfield, else greenfield. State the detection and let the user override.2. **Scan** (brownfield): `index_repository` if needed, then `get_architecture` — clusters seed §6 Core Components. Read `manage_adr` if present; never write it.3. **Interview**: follow `references/interview.md`. Detect project type per `references/project-types.md`.4. **Research**: run `workflows/research.js` per `references/research.md`. Surface dropped items before writing.5. **Write**: model first (`references/likec4.md`), then ARCHITECTURE.md and companions (`references/writing.md`).6. **Validate**: export the model with `node scripts/likec4-export.mjs --dir ... --out ...`, then `node scripts/validate.mjs --arch ... --model ...` (add `--mode brownfield --clusters ...` when applicable). Fix findings; re-run until clean.7. **Render + serve**: follow `references/viewer.md`; report the URL.## DependencyNode ≥ 20 with npm (`npx likec4`). State this upfront; without it, stop before step 5.

Frequently asked questions