skills.rest
skanehira
skanehiraCOMMUNITY
Explore all skills by this author →
𝕏@gorilla0513GitHub

analyzing-requirements

Analyze ambiguous user requirements and generate a structured DESIGN.md document.

88|4|Updated Oct 14, 2018
Search Tags:#architecture#data modeling#API design#requirements analysis#AskUserQuestion#DESIGN.md
One-click install
npx skills add https://github.com/skanehira/dotfiles --skill analyzing-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyzing-requirements
Source: https://github.com/skanehira/dotfiles/tree/main/claude/skills/analyzing-requirements
Command: npx skills add https://github.com/skanehira/dotfiles --skill analyzing-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ユーザー要件の曖昧さを抽出・分析し、DESIGN.md を生成することで、実装の前提を明確化します。MUSTルールの適用、AskUserQuestion による不明点の解消、アーキテクチャ設計の起点となる設計文書の作成を支援します。

Core Features & Use Cases

  • MUSTルールの適用: ../shared/references/must-rules.md に沿って分析を進めます。
  • 不明点の解消: AskUserQuestion を用いて必要な情報をユーザー確認します。
  • アーキテクチャ設計の出発点: 技術選定・データ設計・API設計の要点を含む DESIGN.md を生成します。

Quick Start

要件が不確実な状態で分析を開始し、DESIGN.md 作成の前提条件を満たした段階で DESIGN.md を生成します。必要な質問がある場合は AskUserQuestion で確認します。

Frequently Asked Questions about analyzing-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn unclear requirements into a detailed system design?▼

Analyzing ambiguous requirements produces a comprehensive DESIGN.md document that clarifies architecture, data models, APIs, and non-functional requirements before implementation begins. This structured approach prevents costly rework by establishing shared understanding across teams.

What should a requirements analysis document include?▼

A complete DESIGN.md covers architecture diagrams, data models, API specifications, security considerations, performance requirements, testing strategies, and deployment guidance. This ensures all technical decisions are documented and traceable.

When do I need formal requirements analysis before building?▼

Formal analysis is essential when requirements are unclear, system architecture must be designed from scratch, or large-scale features require detailed planning. It prevents miscommunication and aligns stakeholders on technical approach before development starts.

How do I handle gaps or ambiguities in requirements?▼

Requirements analysis applies structured questioning to surface and resolve unclear points directly with stakeholders. Documenting these clarifications in DESIGN.md creates a single source of truth for implementation decisions.

Can requirements analysis work with evolving or incomplete requirements?▼

Yes. Analysis begins with ambiguous requirements and progressively clarifies them through structured questioning. Once prerequisites are met, it produces a finalized DESIGN.md that guides implementation and enables downstream planning tasks.

Related Skills

Explore More Software Engineering Skills→
shafibabarshafibabar
1

requirements-analysis

Elicit functional requirements from OKRs and stakeholder inputs into traceable documents.

Community
Advanced
SireJeffSireJeff
8

plan

Generate chunk-based implementation plans from structured research documents.

Community
Advanced
Eigo-Mt-FujiEigo-Mt-Fuji

system-architect

Design scalable, secure architectures with C4 diagrams, ADRs, and trade-off analysis.

Community
Advanced
cnfjlhjcnfjlhj
425

all-plan

Coordinate end-to-end feature planning with clarification, review, and plan documentation.

Community
Advanced