feature-analyzer
Comprehensive feature artifact analysis for loading and understanding complete feature context. Use when needing to: (1) Load all feature documentation before implementation, (2) Build mental model of feature requirements and architecture, (3) Prepare context for downstream operations like checklist generation or task execution, (4) Analyze feature completeness and artifact availability. Triggers on: analyze feature, load feature context, prepare feature, check feature prerequisites, understand feature scope.
When & Why to Use This Skill
The Feature Analyzer is a robust Claude skill designed to automate the ingestion and analysis of software feature documentation. By systematically scanning and loading artifacts like specifications, UX flows, and technical plans, it builds a comprehensive mental model that serves as the foundation for accurate implementation, architecture design, and task execution. This skill ensures that all prerequisites are met and context is fully internalized before any development work begins.
Use Cases
- Pre-implementation Context Loading: Automatically ingest all relevant feature documentation (spec, UX, plan, tasks) to ensure the AI agent or developer has a complete understanding of requirements before starting code changes.
- Documentation Gap Analysis: Use the prerequisite scanner to identify missing core artifacts such as specifications or data models, preventing implementation errors caused by incomplete information.
- Downstream Task Preparation: Extract structured insights from feature plans and task lists to generate actionable implementation checklists, TDD cycles, and execution orders.
- Architectural Alignment: Build a unified mental model of system entities, API contracts, and user flows to ensure new code adheres to the defined architecture and UX standards.
| name | feature-analyzer |
|---|---|
| description | Comprehensive feature artifact analysis for loading and understanding complete feature context. Use when needing to: (1) Load all feature documentation before implementation, (2) Build mental model of feature requirements and architecture, (3) Prepare context for downstream operations like checklist generation or task execution, (4) Analyze feature completeness and artifact availability. Triggers on: analyze feature, load feature context, prepare feature, check feature prerequisites, understand feature scope. |
| allowed-tools | Read, Write, Bash (*) |
Feature Analyzer
Load and analyze all feature artifacts to build comprehensive understanding for downstream operations.
Workflow Overview
- Scan - Check artifact availability
- Load - Read all feature documents
- Build - Construct complete mental model
- Confirm - Ready for operations
Step 1: Scan Feature Directory
Run prerequisites scanner to identify available artifacts:
.claude/skills/feature-analyzer/scripts/check-prerequisites.sh <feature-directory>
Scanner checks for:
- Core artifacts: spec.md, ux.md, plan.md, tasks.md
- Data artifacts: data-model.md, contracts/
- Support artifacts: research.md, setup.md
Outputs JSON with AVAILABLE and MISSING arrays. Exits with error if core files missing.
Step 2: Load Feature Artifacts
Read all available artifacts in priority order:
Core Documents (Required)
spec.md- Requirements (FR-XXX), user stories, acceptance criteriaux.md- User flows, interactions, states, errorsplan.md- Architecture, components, technology stacktasks.md- Implementation phases, TDD cycles, execution order
Data & Contracts
data-model.md- Entities, validation, state machinescontracts/- APIs, messages, schemas- openapi.yaml
- contracts.md
Supporting Documents
research.md- Technical decisions, rationalesetup.md- Environment, dependencies, commands
Step 3: Build Mental Model
Extract and internalize from each artifact:
From spec.md:
- Main journey and goal
- All requirements with IDs
- Test scenarios
- Edge cases and constraints
From ux.md:
- Complete flow with triggers
- States and transitions
- Error handling patterns
From plan.md:
- Code structure (A/B/C/D patterns)
- Requirement→Component mapping
- Technical constraints
From tasks.md:
- Implementation sequence
- TDD coverage targets
- File creation paths
- Dependencies
From data-model.md:
- Field definitions and rules
- Constants and limits
- Entity relationships
From contracts:
- Endpoint specifications
- Message formats
- Protocol definitions
Step 4: Confirm Readiness
Output minimal confirmation:
✅ Feature context loaded: [feature-name]
Available: [list of loaded artifacts]
Ready for: implementation | checklist | queries
Error Handling
- Missing core files: Stop and report specific missing file
- Malformed content: Report file and parsing error
- Access denied: Report permission issue
Usage Notes
This skill prepares context for:
- Task execution (implementation from tasks.md)
- Checklist generation (requirements validation)
- Architecture queries
- Technical guidance
Context remains in memory for entire conversation.