How do I install the Business Analyst skill?

Run npx skillmds add vukhanhtruong/business-analyst 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 Business Analyst 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 Business Analyst?

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 Business Analyst free to use?

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

Who published Business Analyst?

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

Business Analyst by vukhanhtruong — Agent Skill

Name: Business Analyst
Rating: 4.666666666666667 (3 reviews)
Author: vukhanhtruong

Business Analyst

Interview-driven requirements discovery — turn raw client input (emails, notes, transcripts, briefs) into a validated, traceable requirements package before solution architecture. Use when the user asks to analyze client requirements, run discovery on a lead, clarify a vague request, build a BA requirements package, or prepare requirements for architecture and estimation.

vukhanhtruong 9dd5fce 18 files · 60.9 KB Updated Sep 10, 2026

File contents

business-analyst

Turn incomplete client input into two artifacts in the lead directory: requirements.md (five parts, human-readable) and requirements.json (machine handoff for analyze-requirements, estimate, and proposal).

Hard rules

Never invent requirements — every material fact carries a label (confirmed | assumed | recommended) and a source. A recommendation never renders as a confirmed requirement.
Problem before solution — no technology recommendations, no architecture. This skill stops at WHAT; HOW belongs to analyze-requirements and later skills.
Unknowns render as open questions, never silently filled. Distinguish unknown (client doesn't know) from undecided (client must choose).
Never block on unanswered questions — write the package with an honest status and readiness; a re-run refines it, never restarts the interview.
Every requirement carries a stable ID and traceability links; node scripts/validate.mjs must exit 0 before the package is final.
The human reviews requirements.md before status may become READY_FOR_ARCHITECTURE.

Flow

Detect evidence: input documents? an existing requirements.json (re-run — see Re-run)? greenfield or existing system? State findings; the user can override.
Depth: ask QUICK / STANDARD / DEEP first (references/interview.md §6).
Extract: pull every known goal, actor, process, rule, constraint, integration, and assumption from ALL inputs before asking anything.
Gap analysis: extracted knowledge vs the nine layers (references/interview.md §4) → prioritized P1/P2/P3 gap list.
Select frameworks: from references/frameworks.md — justify each pick in one line; never apply all.
Interview: per references/interview.md — grouped, adaptive, contradiction-challenging, example-hungry. Solution involves AI or agents → also work through references/ai-extension.md.
Write: requirements.md + requirements.json per references/writing.md.
Validate: node scripts/validate.mjs --json <dir>/requirements.json --md <dir>/requirements.md — fix findings, re-run until clean. No Node in the environment (e.g. the claude.ai sandbox) → run python3 scripts/validate.py with the same flags; identical checks.
Fresh-eyes review: dispatch a subagent per references/review.md; apply findings, re-validate; one cycle max.
Human review: show Part 5 (readiness report); the human confirms the status. Only they can promote it to READY_FOR_ARCHITECTURE.

Re-run

requirements.json already exists → diff the new answers and material into the registers (answer open questions, confirm assumptions, add findings), keep every existing ID stable, recompute readiness, and advance the status. Never restart the interview; ask only what is still open.

Handoff

Downstream skills treat requirements.json as detected evidence — never a prerequisite. FR/BR/ASM/Q ids are stable so architecture decisions and estimates can cite them.

Dependency

Node ≥ 20, or Python ≥ 3.10 where Node is unavailable (scripts/validate.py is a parity-tested port of scripts/validate.mjs). Scripts are dependency-free either way.

---name: business-analystdescription: Interview-driven requirements discovery — turn raw client input (emails, notes, transcripts, briefs) into a validated, traceable requirements package before solution architecture. Use when the user asks to analyze client requirements, run discovery on a lead, clarify a vague request, build a BA requirements package, or prepare requirements for architecture and estimation.---# business-analystTurn incomplete client input into two artifacts in the lead directory:`requirements.md` (five parts, human-readable) and `requirements.json`(machine handoff for analyze-requirements, estimate, and proposal).## Hard rules1. Never invent requirements — every material fact carries a label (`confirmed` | `assumed` | `recommended`) and a source. A recommendation never renders as a confirmed requirement.2. Problem before solution — no technology recommendations, no architecture. This skill stops at WHAT; HOW belongs to analyze-requirements and later skills.3. Unknowns render as open questions, never silently filled. Distinguish unknown (client doesn't know) from undecided (client must choose).4. Never block on unanswered questions — write the package with an honest status and readiness; a re-run refines it, never restarts the interview.5. Every requirement carries a stable ID and traceability links; `node scripts/validate.mjs` must exit 0 before the package is final.6. The human reviews requirements.md before status may become `READY_FOR_ARCHITECTURE`.## Flow1. **Detect evidence**: input documents? an existing `requirements.json` (re-run — see Re-run)? greenfield or existing system? State findings; the user can override.2. **Depth**: ask QUICK / STANDARD / DEEP first (`references/interview.md` §6).3. **Extract**: pull every known goal, actor, process, rule, constraint, integration, and assumption from ALL inputs before asking anything.4. **Gap analysis**: extracted knowledge vs the nine layers (`references/interview.md` §4) → prioritized P1/P2/P3 gap list.5. **Select frameworks**: from `references/frameworks.md` — justify each pick in one line; never apply all.6. **Interview**: per `references/interview.md` — grouped, adaptive, contradiction-challenging, example-hungry. Solution involves AI or agents → also work through `references/ai-extension.md`.7. **Write**: requirements.md + requirements.json per `references/writing.md`.8. **Validate**: `node scripts/validate.mjs --json <dir>/requirements.json --md <dir>/requirements.md` — fix findings, re-run until clean. No Node in the environment (e.g. the claude.ai sandbox) → run `python3 scripts/validate.py` with the same flags; identical checks.9. **Fresh-eyes review**: dispatch a subagent per `references/review.md`; apply findings, re-validate; one cycle max.10. **Human review**: show Part 5 (readiness report); the human confirms the status. Only they can promote it to `READY_FOR_ARCHITECTURE`.## Re-run`requirements.json` already exists → diff the new answers and material intothe registers (answer open questions, confirm assumptions, add findings),keep every existing ID stable, recompute readiness, and advance the status.Never restart the interview; ask only what is still open.## HandoffDownstream skills treat `requirements.json` as detected evidence — never aprerequisite. FR/BR/ASM/Q ids are stable so architecture decisions andestimates can cite them.## DependencyNode ≥ 20, or Python ≥ 3.10 where Node is unavailable (`scripts/validate.py`is a parity-tested port of `scripts/validate.mjs`). Scripts aredependency-free either way.

Frequently asked questions