Claude skill
Req Analyze
Req Analyze is a Claude skill in the Sd0x Harness plugin. Requirements analysis — problem decomposition, stakeholder scan, requirement structuring.
What it does
The description in the skill's SKILL.md, which Claude reads to decide when to use it:
Requirements analysis — problem decomposition, stakeholder scan, requirement structuring. Produces 1-requirements.md (Phase 1 lifecycle doc, NOT the per-task request ticket — for those use /create-request). Use when: analyzing needs before tech spec, decomposing requirements, stakeholder analysis, 需求分析. Not for: solution comparison (use feasibility-study), tech design (use tech-spec), per-task tracking tickets (use create-request), issue root cause (use issue-analyze).
The skill's instructions (about 2,136 words) cover:
- Trigger
- When NOT to Use
- Boundary Contract
- Relationship with /create-request
- Workflow ordering
- Anti-patterns to avoid
- Usage
- Arguments
- Workflow
- Phase 0: Context Resolution
- Path Validation
- Scope Gate
How to use it
- Req Analyze comes inside the Sd0x Harness plugin, so you get it by installing that plugin, along with its 101 other skills. A plugin installs as one unit, with all its skills. The plugin's page has the install steps, and plugins are saved to your Claude account.
- Ask Claude for the task. When your request matches the skill's description, Claude loads it.
- To pick it yourself in Claude chat, type
/or click + and choose req-analyze. In Claude Code and Cowork, type:/sd0x-dev-flow:req-analyze
Source
- Plugin
- Sd0x Harness
- SKILL.md
- View on GitHub
- Repo stars
- 196
- Repo last pushed
- Nov 16, 2026
- Checked
- Nov 16, 2026
More skills in Sd0x Harness
- Request TrackingRequest tracking knowledge base. Use when: querying request status, managing document references, tracking progress.
- Review SpecReview technical spec documents from completeness, feasibility, risk, and code consistency perspectives.
- Risk AssessUncommitted code risk assessment with breaking change detection, blast radius analysis, and scope metrics.
- RunbookGenerate and update feature release runbooks from existing docs and codebase.
- Safe RemoveSafely remove plugin assets (skill/agent/rule/script/hook) with dependency detection and reference cleanup.
- Security ReviewSecurity review via Codex exec. Use when: OWASP Top 10:2025 audit, dependency vulnerability check, security-sensitive changes.
- Seek VerdictIndependent second-opinion verification for any finding.
- SharinganReplicate knowledge from any source as sd0x-dev-flow skill definition.
- SimplifyWrap-up refactoring — simplify code, eliminate duplication, preserve behavior
- Skill Health CheckValidate skill quality against routing, progressive loading, and verification criteria.
- Smart CommitSmart batch commit. Analyzes uncommitted changes, groups by cohesion, generates commit messages matching project style.
- Smart RebaseSmart partial rebase for squash-merge repositories.
- Statusline ConfigCustomize Claude Code statusline. Use when: user says 'statusline', 'status line', 'customize statusline', 'modify statusline', 'statusline settings', 'statusline theme', 'change theme', 'color…
- Tech BriefTechnical briefing for developer sharing.
- Tech SpecTech spec generation and review. Use when: designing features, writing specs, spec review.
- Test DeepContext-aware test orchestration. Use when: smart test selection, failure triage, progressive test ladder, test failure analysis.
- Test HealthHolistic test coverage measurement. Use when: assessing test health, measuring coverage trends, quantitative + qualitative test audit.
- Test ReviewTest coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit.
- UI First PrinciplesFirst-principles UI/IA reasoning: turns a `<scenario>` + API field set into JTBD analysis, principle-anchored field-priority decisions, anti-pattern findings, and a bidirectional UI↔API gap report.
- Update DocsResearch current code state then update corresponding docs, ensuring docs stay in sync with code.
- VerifyVerification loop — lint -> typecheck -> unit -> integration -> e2e
- Watch CiMonitor GitHub Actions CI runs until completion.
- Zh TwRewrite the previous reply in Traditional Chinese
- AdrWrite an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature>/adr-<NNN>-<title>.md with a 3-digit…