analyze

Validate spec → plan → tasks chain consistency before implementation.

12 stars

bylionbenjamin

View on GitHub Installation ↓

Best use case

analyze is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Validate spec → plan → tasks chain consistency before implementation.

Teams using analyze 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

$curl -o ~/.claude/skills/analyze/SKILL.md --create-dirs "https://raw.githubusercontent.com/lionbenjamin/agent-templates/main/skills/analyze/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/analyze/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How analyze Compares

Feature / Agent	analyze	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?

Validate spec → plan → tasks chain consistency before implementation.

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

# Analyze Skill

Validate development pipeline consistency and traceability.

## When to Activate

This skill is relevant when:
- Validating spec-to-plan alignment
- Checking plan-to-tasks consistency
- Finding gaps before implementation
- Ensuring traceability across artifacts
- Pre-implementation pipeline validation

## Core Principles

### Traceability First
- Every task must trace back to a requirement
- Map user stories to implementation items
- Verify acceptance criteria coverage
- End-to-end requirement tracking

### Gap Detection
- Find what's missing before code is written
- Identify uncovered acceptance criteria
- Locate orphaned tasks or plan items
- Catch missing edge cases early

### Consistency Guardian
- Ensure plans match specs
- Ensure tasks match plans
- Flag misalignments immediately
- Maintain artifact coherence

### Coverage Validation
- Verify all spec requirements have plans
- Confirm all plan items have tasks
- Check non-functional requirements
- Validate test coverage planning

## Quick Checks

For consistency analysis, verify:
- [ ] Specification file exists and loaded
- [ ] Implementation plan exists and loaded
- [ ] Task breakdown exists and loaded
- [ ] Every user story maps to plan items
- [ ] Every acceptance criterion has implementation
- [ ] Every plan change has corresponding tasks
- [ ] Verification items reflected in tasks
- [ ] No orphan tasks without spec backing
- [ ] No plan items without requirements
- [ ] Test tasks exist for acceptance criteria
- [ ] Edge cases have corresponding tasks
- [ ] Non-functional requirements covered
- [ ] Performance requirements have tasks
- [ ] Security requirements have tasks
- [ ] All gaps documented

## Analysis Output

### Traceability Matrix
Map spec items to plan sections to tasks with status

### Gap Categories
- Missing coverage areas
- Orphaned items without backing
- Incomplete implementations

### Report Format
- Overall health: CONSISTENT / GAPS FOUND / MAJOR ISSUES
- Aligned items with full traceability
- Gaps requiring attention
- Prioritized recommendations