skills.rest
nm7-jp
nm7-jpCOMMUNITY
Explore all skills by this author →
GitHub

analyzing-requirements

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

Updated Aug 23, 2026
Search Tags:#architecture#documentation#requirements#analyze#system-design#design-doc#design-document
One-click install
npx skills add https://github.com/nm7-jp/morpheus-operator --skill analyzing-requirements-nm7-jp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyzing-requirements
Source: https://github.com/nm7-jp/morpheus-operator/tree/main/.claude/skills/analyzing-requirements
Command: npx skills add https://github.com/nm7-jp/morpheus-operator --skill analyzing-requirements-nm7-jp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms ambiguous user requirements into actionable design artifacts (DESIGN.md), clarifying uncertainties, validating feasibility, and outlining architecture and technical approach.

Core Features & Use Cases

  • Generate a structured DESIGN.md containing system overview, functional and non-functional requirements, architecture decisions, data design, API planning, and deployment considerations.
  • Identify ambiguities and suggest clarifying questions to stakeholders to reduce risk and rework.
  • Provide a clear traceability of requirements to design decisions and engineering tasks.

Quick Start

Analyze the current user requirements and generate a comprehensive DESIGN.md with architecture decisions and design guidance.

Frequently Asked Questions about analyzing-requirements

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

FAQPage Schema
How do I generate a design document from ambiguous user requirements?▼

Generating a design document from ambiguous user requirements involves analyzing the specifications to produce a structured DESIGN.md. This includes defining functional and non-functional requirements, architecture decisions, data design, API planning, and deployment considerations.

What is the best way to identify ambiguities in complex system design specifications?▼

The best way to identify ambiguities in complex system design specifications is to analyze the requirements and generate clarifying questions for stakeholders. This reduces risk and rework by validating feasibility before architecture decisions are finalized.

Can I use this to create architecture decisions for projects with large feature sets?▼

Yes, this approach is applicable to projects with large feature sets needing formal design artifacts. It analyzes your requirements to outline architecture decisions and the technical approach within a structured DESIGN.md.

How do I trace user requirements to engineering tasks in a design doc?▼

You can trace user requirements to engineering tasks by generating a DESIGN.md that provides clear traceability from requirements to design decisions. This ensures every architecture choice links back to a specified functional or non-functional need.

When do I need a formal DESIGN.md artifact instead of just coding the feature?▼

You need a formal DESIGN.md artifact instead of just coding when dealing with vague specifications, complex architectures, or large feature sets. It validates feasibility and clarifies uncertainties before development begins.

Related Skills

Explore More Software Engineering Skills→
TykoDevTykoDev
9

researcher

Convert raw user input into an RFC 2119-prioritized SRS with acceptance criteria.

Community
Advanced
hikchhikch

update-design

Record design decisions from conversations into DESIGN.md with dated changelog entries.

Community
Intermediate
romiluz13romiluz13
161

architecture-patterns

Translate functionality requirements into architecture patterns with C4-inspired views.

Community
Intermediate
thapaliyabikendrathapaliyabikendra
24

technical-design-patterns

Create technical design documents for ABP Framework features.

Community
Basic