Skill Construction Roadmap
Organize the classification system, evaluation criteria, dependency relationships, and construction plans for Skills.
About This Document
This document formalizes Discussion #20 (Skill Construction Strategy Map) as an official project document.
While MCPs handle "real-time access to external data," Skills handle "static knowledge and judgment criteria" (see 03-architecture.md). For the MCP construction strategy, see mcp-roadmap.md. For composition patterns, see composition-patterns.md.
5 Skill Types
All Skills are "static knowledge," but the structure differs depending on the type of knowledge.
| Type | Form of AI Instruction | Approximate Volume |
|---|---|---|
| Principle Type | "Determine whether this violates the principle" | Short (1-3 pages) |
| Pattern Type | "Select an applicable pattern for this situation" | Long (proportional to number of patterns) |
| Methodology Type | "Execute following this process" | Medium |
| Checklist Type | "Check all items and report the results" | Short |
| Guideline Type | "Improve according to this guideline" | Medium |
5-Axis Skill Evaluation
Skill-specific evaluation criteria corresponding to MCP's 5 axes (Governing Body, Openness, Machine Readability, Structural Clarity, Practical Use Cases).
| Axis | Meaning |
|---|---|
| Knowledge Stability | How frequently it is updated (Stable ◎ to Volatile △) |
| Scope Clarity | Whether the boundary with other Skills is clear |
| Trigger Clarity | Whether it is possible to determine when to use it |
| Standalone Completeness | Whether it can deliver value alone, or requires other Skills |
| Verifiability | Whether the effect can be objectively measured |
Individual Skill Evaluations
Foundation Skills
| Skill | Type | Stability | Scope | Trigger | Standalone | Verifiability |
|---|---|---|---|---|---|---|
| SOLID | Principle | ◎ | ◎ | ◎ | ◎ | ○ |
| Clean Code | Guideline | ◎ | ○ | ◎ | ◎ | △ |
| TDD | Methodology | ◎ | ◎ | ◎ | ◎ | ◎ |
Design Skills
| Skill | Type | Stability | Scope | Trigger | Standalone | Verifiability |
|---|---|---|---|---|---|---|
| Design Patterns | Pattern | ◎ | ◎ | ○ | ○ | ○ |
| Clean Architecture | Principle | ◎ | ◎ | ○ | ○ | ◎ |
| DDD | Methodology | ◎ | △ | △ | △ | △ |
Testing Skills
| Skill | Type | Stability | Scope | Trigger | Standalone | Verifiability |
|---|---|---|---|---|---|---|
| Test Patterns | Pattern | ○ | ○ | ◎ | ○ | ◎ |
| BDD | Methodology | ◎ | ◎ | ○ | ◎ | ◎ |
| Coverage Strategy | Checklist | ○ | ◎ | ◎ | ○ | ◎ |
Infrastructure & Architecture Skills
| Skill | Type | Stability | Scope | Trigger | Standalone | Verifiability |
|---|---|---|---|---|---|---|
| 12 Factor App | Principle | ◎ | ◎ | ○ | ◎ | ◎ |
| Microservices | Pattern | ○ | △ | △ | △ | △ |
| EIP | Pattern | ◎ | ◎ | ○ | ○ | ○ |
| IaC Patterns | Pattern | ○ | ○ | ○ | ◎ | ○ |
Quality Improvement Skills
| Skill | Type | Stability | Scope | Trigger | Standalone | Verifiability |
|---|---|---|---|---|---|---|
| Refactoring | Pattern | ◎ | ◎ | ◎ | ○ | ○ |
Skill Dependency Relationships
Skills have a clear dependency hierarchy. While MCPs can be built independently, Skills require a build order that considers dependencies.
Trigger Contexts — When to Use
Skills tend to have ambiguous "when to trigger" conditions. Here we organize them by context-based Skill sets.
| Context | Triggered Skills | Combination Purpose |
|---|---|---|
| Writing Code | Clean Code | Constant reference for naming and function design standards |
| Code Review | SOLID + Clean Code + Refactoring | Detect principle violations → Identify smells → Suggest improvements |
| Architecture Design | DDD + Clean Architecture + 12 Factor | Domain modeling → Layer design → Cloud readiness |
| Test Design | TDD + BDD + Test Patterns + Coverage | Process → Scenarios → Pattern application → Coverage assessment |
| Refactoring | Refactoring + Design Patterns + SOLID | Detect smells → Apply patterns → Verify principle compliance |
| Infrastructure Design | 12 Factor + Microservices + IaC + EIP | Cloud-native → Decomposition → Automation → Integration |
For details on multi-Skill simultaneous trigger patterns, see composition-patterns.md.
Challenges of "Ambiguity" and Countermeasures
Skill design has unique challenges that MCPs do not face.
Challenge 1: Scope Overlap
Is "SRP (Single Responsibility Principle)" part of the SOLID Skill or the Clean Code Skill?
Countermeasure: Place the definition of the principle in the SOLID Skill, and reference it as an application example in Clean Code. Establish a "primary source of definition" among Skills.
Challenge 2: Granularity Decisions
Should DDD be one Skill? Or should it be split into Strategic Patterns and Tactical Patterns?
Countermeasure: If the trigger context is the same, keep it as one. Start with one and decide on separation through operational experience.
Challenge 3: Quality Measurement
How do you measure "Is this a good Skill?"
Countermeasure: Measure using the following indirect metrics.
| Metric | Measurement Method |
|---|---|
| AI Judgment Accuracy | Whether review feedback became more accurate after Skill application |
| Trigger Appropriateness | Whether it avoids triggering in unnecessary situations and triggers in necessary ones |
| Context Efficiency | The effect gained relative to token consumption from Skill references |
Priority Roadmap
Build order considering dependencies and practical relevance.
Related Documents
- Discussion #20: Skill Construction Strategy Map — The Discussion that this document is based on
- mcp-roadmap.md — MCP Construction Roadmap
- composition-patterns.md — Composition Patterns
- concepts/03-architecture.md — Skill Definitions and Layer Structure
- skills/creating-skills.md — Skill Creation Guide