analyzing-requirements
Helps the user define, refine, and document requirements for new software features or projects. Use this when a user says "I want to build...", "I need a feature...", or "How should I implement...".
Best use case
analyzing-requirements is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Helps the user define, refine, and document requirements for new software features or projects. Use this when a user says "I want to build...", "I need a feature...", or "How should I implement...".
Teams using analyzing-requirements should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/analyzing-requirements/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How analyzing-requirements Compares
| Feature / Agent | analyzing-requirements | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Helps the user define, refine, and document requirements for new software features or projects. Use this when a user says "I want to build...", "I need a feature...", or "How should I implement...".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Analyzing Requirements You are an expert Business Analyst and Technical Architect. Your goal is to transform vague feature requests into precise, buildable specifications by asking deep-detail questions. ## Workflow 1. **Acknowledge & Contextualize**: Summarize what you understand so far about the feature. 2. **Phase 1: The "Why" and "Who"**: Before "What," establish the business goal and the target persona. 3. **Phase 2: Deep Detail Elicitation**: Use the `AskUserQuestion` tool to present multiple-choice opinions or open questions. 4. **Phase 3: Edge Case Discovery**: Proactively suggest 2-3 potential "what if" scenarios (e.g., "What if the user is offline?"). 5. **Phase 4: Synthesis**: Generate a structured Requirement Summary including User Stories and Acceptance Criteria. ## Guidelines for Questions - **Avoid Yes/No**: Ask "How should X behave?" instead of "Should X behave like this?". - **Opinionated Choices**: Provide 3 potential implementation "opinions" (e.g., "Opinion A: Simple MVP, Opinion B: Robust/Scalable, Opinion C: High-Performance"). - **Technical Guardrails**: Always ask about existing tech stack and data privacy. ## Reference See `PROMPTS.md` for specific question banks categorized by feature type.
Related Skills
doc-sys: Create System Requirements (Layer 6)
Create System Requirements (SYS) - Layer 6 artifact defining functional requirements and quality attributes
awesome-copilot-root-atlassian-requirements-to-jira
Transform requirements documents into structured Jira epics and user stories with intelligent duplicate detection, change management, and user-approved creation workflow. Use when: the task directly matches atlassian requirements to jira responsibilities within plugin awesome-copilot-root. Do not use when: a more specific framework or task-focused skill is clearly a better match.
analyzing-business-models
Analyzes business models including revenue models, unit economics, competitive moats, scalability, and value creation/capture mechanisms using frameworks like Business Model Canvas and strategic analysis. Use when the user requests business model analysis, unit economics review, moat assessment, or wants to understand how a company creates and captures value.
analyzing-websites
既存ウェブサイトを分析し、サイトマップとワイヤーフレームを作成します。URLを渡すとページ構造を解析し、指定形式で出力します。コンテンツ分析機能でページの目的やターゲットも要約できます。
analyzing-specifications
Use when analyzing requirements or project specifications - guides shannon analyze command, explains 8D complexity output, caching behavior, context-aware mode with --project flag
analyzing-source
Conducts in-depth analysis of a specific source or topic, producing comprehensive summaries for research synthesis. Use when you need detailed analysis and documentation of individual sources as part of a larger research effort.
analyzing-pricing
Analyzes pricing strategies, competitive pricing benchmarks, pricing models, value metrics, and willingness-to-pay to optimize pricing and positioning. Use when the user requests pricing analysis, competitive pricing comparison, pricing strategy, pricing model evaluation, or wants to optimize pricing decisions.
analyzing-financial-statements
This skill calculates key financial ratios and metrics from financial statement data for investment analysis
spec-requirements
Generate comprehensive requirements definition documents with technology selection and improvement suggestions
requirements-gathering
Systematic requirements gathering through AskUserQuestion. Use when starting development to clarify app specifications.
analyzing-user-feedback
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
analyzing-unknown-codebases
Analyze unfamiliar codebases systematically to produce subsystem catalog entries - emphasizes strict contract compliance and confidence marking