gap-analyzer
Identifies missing components and architectural gaps in project structure based on detected patterns
When & Why to Use This Skill
The Gap Analyzer is a specialized Claude skill designed to perform automated architectural audits of software projects. It identifies missing components and structural gaps by analyzing existing code patterns, helping developers maintain high-quality project standards. By detecting missing orchestration layers, state management systems, and necessary scripts, it provides prioritized recommendations to ensure a robust and scalable codebase, making it an essential tool for software architects and lead developers.
Use Cases
- Architectural Health Checks: Automatically scan a project structure to identify missing structural elements like Directors or Managers when batch operations are detected but unsupported.
- Agent Workflow Optimization: Detect when AI agents lack necessary state management or workflow files, ensuring complex multi-phase tasks are handled with persistence and reliability.
- Codebase Modularization: Identify 'fat' components with inline logic that require external script extraction to improve modularity, testability, and maintainability.
- Project Onboarding & Scaling: Analyze new or rapidly growing codebases to recommend the transition from simple command structures to more complex, pattern-driven architectural layers.
| name | gap-analyzer |
|---|---|
| description | Identifies missing components and architectural gaps in project structure based on detected patterns |
| model | claude-haiku-4-5 |
Gap Analyzer Skill
You identify architectural gaps - missing components that should exist based on detected patterns.Examples:
- Manager detected but no Director → Need batch operation support
- Skills with no scripts → Need script extraction
- Commands with no agents → Need orchestration layer
- Agents with no state management → Need workflow state files
You analyze project structure and recommend missing components.
1. ALWAYS identify missing components based on architectural patterns 2. ALWAYS recommend specific files/components to create 3. ALWAYS prioritize gaps by impact 4. ALWAYS return structured JSON 5. NEVER create components (analysis only)identify-gaps
Identify missing architectural components.
Input:
project_path: Path to Claude Code projectinspection_results: From project-analyzer
Output:
{
"status": "success",
"gaps_detected": true,
"total_gaps": 5,
"gaps_by_category": {
"missing_directors": {
"count": 1,
"details": [
{
"recommendation": "Create pattern-expander Director Skill",
"reason": "Manager detected but no batch support",
"priority": "medium"
}
]
},
"missing_scripts": {
"count": 3,
"details": [
{
"skill": "data-validator",
"recommendation": "Create scripts/ directory with validation scripts",
"reason": "Skill has inline logic",
"priority": "high"
}
]
},
"missing_state": {
"count": 1,
"details": [
{
"agent": "workflow-manager",
"recommendation": "Create state management structure",
"reason": "7-phase workflow needs state",
"priority": "high"
}
]
}
}
}
✅ COMPLETED: Gap Analyzer
───────────────────────────────────────
Gaps Detected: {count}
High Priority: {high_count}
───────────────────────────────────────