spdd-analysis

Analyze business requirements and codebase context to generate strategic REASONS Canvas context.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/undertext/spdd-skills --skill spdd-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spdd-analysis
Source: https://github.com/undertext/spdd-skills/tree/main/skills/core/spdd-analysis
Command: npx skills add https://github.com/undertext/spdd-skills --skill spdd-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill analyzes business requirements and the codebase context to provide a strategic-level enriched context, facilitating the creation of REASONS Canvas prompts.

Core Features & Use Cases

  • Strategic Analysis: Combines business information, domain concepts, high-level approach decisions, and risk analysis.
  • Codebase Exploration: Uses concept-driven scoping to explore relevant parts of the codebase.
  • Domain Concept Identification: Identifies existing and new business concepts and their relationships.
  • Strategic Approach & Trade-offs: Determines high-level solution direction and key design decisions.
  • Risk & Gap Analysis: Surfaces ambiguities, edge cases, technical risks, and AC coverage.
  • Use Case: Automate the analysis of a new feature requirement to identify potential issues and propose strategic solutions before design begins.

Quick Start

Run the /spdd-analysis command followed by the business requirement description or file reference.

Frequently Asked Questions about spdd-analysis

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

FAQPage Schema
How do I analyze business requirements and codebase context for strategic planning?

Requirements analysis combines business information with concept-driven codebase exploration to generate strategic-level enriched context, identifying domain concepts, trade-offs, and technical risks before design begins.

What is the best way to identify domain concepts and risks before starting software design?

Strategic analysis automates the review of new feature requirements to surface domain concept relationships, ambiguities, edge cases, and acceptance criteria coverage, proposing high-level solution directions.

How do I generate enriched context for a REASONS Canvas from a new feature requirement?

You can generate enriched context by running the analysis command followed by the business requirement description or file reference, which processes domain concepts and codebase structure to produce strategic context.

Do I need prior knowledge of the business domain and codebase structure to perform codebase analysis?

Yes, effective codebase analysis requires existing knowledge of the business domain and codebase structure to accurately identify relevant concepts, perform scoping, and determine high-level design decisions.

What strategic planning trade-offs and design decisions can I extract from codebase exploration?

Codebase exploration identifies high-level solution directions, key design decisions, and strategic trade-offs by combining business information with concept-driven scoping to map existing and new business concepts.

Why does business analysis fail to surface technical risks and edge cases in new features?

Business analysis often misses technical risks when it lacks concept-driven codebase scoping; strategic analysis solves this by mapping domain concepts to the codebase to expose ambiguities and AC coverage gaps.