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
Best use case
analyzing-specifications is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when analyzing requirements or project specifications - guides shannon analyze command, explains 8D complexity output, caching behavior, context-aware mode with --project flag
Teams using analyzing-specifications 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-specifications/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How analyzing-specifications Compares
| Feature / Agent | analyzing-specifications | 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?
Use when analyzing requirements or project specifications - guides shannon analyze command, explains 8D complexity output, caching behavior, context-aware mode with --project flag
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 Specifications ## Overview shannon analyze invokes Shannon Framework spec-analysis skill to perform 8D complexity analysis with automatic caching. ## Basic Usage ```bash shannon analyze project_spec.md shannon analyze spec.md --json > analysis.json shannon analyze spec.md --project myapp # Context-aware ``` ## Output Interpretation **8D Complexity Score** (0.00-1.00): - 0.00-0.30: Simple (hours-1 day, 1-2 agents) - 0.30-0.50: Moderate (1-2 days, 2-3 agents) - 0.50-0.70: Complex (2-4 days, 3-7 agents) - 0.70-0.85: High (1-2 weeks, 8-15 agents) - 0.85-1.00: Critical (2+ weeks, 15-25 agents) **Domain Distribution**: Frontend, Backend, Database, Mobile, DevOps percentages **Phase Plan**: 5 phases with timelines and tasks ## Caching Automatic: - First run: API call (~$0.02, 30-60s) - Second run: Cache hit (<500ms, $0.00) - TTL: 7 days - Check: shannon cache stats ## Context-Aware Mode For existing projects: ```bash # 1. Onboard project first shannon onboard /path/to/project --project-id myapp # 2. Analyze with context shannon analyze new_feature.md --project myapp ``` With context: Mentions existing modules, patterns, tech stack. Without context: Generic recommendations. ## Options - `--json`: JSON output for automation - `--project ID`: Context-aware analysis - `--no-cache`: Skip cache (force fresh analysis) - `--session-id ID`: Custom session tracking
Related Skills
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
api-specifications
Guidance for Splits Network REST API design, implementation, and documentation
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
analyzing-text-patterns
Extract and analyze recurring patterns from log messages, span names, and event names using punctuation-based template discovery. Use when you need to understand log diversity, identify common message structures, detect unusual formats, or prepare for log parser development. Works by removing variable content and preserving structural markers.
analyzing-taint-flow
Tracks untrusted input propagation from sources to sinks in binary code to identify injection vulnerabilities. Use when analyzing data flow, tracing user input to dangerous functions, or detecting command/SQL injection.
Analyzing Spreadsheets
Analyzes Excel spreadsheets, summarizes trends, and recommends charts when users mention spreadsheets, Excel workbooks, or .xlsx files.
analyzing-research-papers
Expert methodology for analyzing and summarizing research papers, extracting key contributions, methodological details, and contextualizing findings. Use when reading papers from PDFs, DOIs, or URLs to create structured summaries for researchers.
analyzing-projects
Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"
analyzing-patterns
Automatically activated when user asks to "find patterns in...", "identify repeated code...", "analyze the architecture...", "what design patterns are used...", or needs to understand code organization, recurring structures, or architectural decisions