Requirements Analysis (req-analyze)

What it does

This skill guides structured requirements analysis: it performs first‑principles decomposition (5‑Why), builds an assumptions register, runs a mandatory stakeholder scan, and (depending on flags) conducts code and web research to produce a 1-requirements.md lifecycle document. It enforces scope boundaries (problem-space only) and avoids solution recommendations or implementation estimates.

When to use it

Use /req-analyze when you need to formalize feature requirements before design: clarifying the root problem, stakeholders, constraints, and acceptance signals. It is not for writing tech specs, creating per-task tickets, or architecture design. Use flags like --quick/--standard/--deep to control research depth.

What's included

• Scripts: guidance and CLI helpers are referenced (feature resolver and research agents).
• References: templates, research-cascade, and output templates are included in the repo references.
• Instructions: boundary contract, workflow phases, path/slug validation rules, and security guardrails (secret redaction, path checks).

Compatible agents

Designed for Claude/agent harness environments that support background exploration agents, web fetch/search tools, and AskUserQuestion interactions. Also integrates with codex-brainstorm for deep completeness checks.