task-analyzer
元认知任务分析和技能选择。分析任务本质、估算规模,并返回带元数据的适当技能。
📖 中文导读:元认知任务分析和技能选择。分析任务本质、估算规模,并返回带元数据的适当技能。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
name: task-analyzer description: Performs metacognitive task analysis and skill selection. Use when determining task complexity, selecting appropriate skills, or estimating work scale. Returns skills with confidence scores and metadata.
Task Analyzer
Provides metacognitive task analysis and skill selection guidance.
Skills Index
See skills-index.yaml for available skills metadata.
Task Analysis Process
1. Understand Task Essence
Identify the fundamental purpose beyond surface-level work:
| Surface Work | Fundamental Purpose |
|---|---|
| "Fix this bug" | Problem solving, root cause analysis |
| "Implement this feature" | Feature addition, value delivery |
| "Refactor this code" | Quality improvement, maintainability |
| "Update this file" | Change management, consistency |
Key Questions:
- What problem are we really solving?
- What is the expected outcome?
- What could go wrong if we approach this superficially?
2. Estimate Task Scale
| Scale | File Count | Indicators |
|---|---|---|
| Small | 1-2 | Single function/component change |
| Medium | 3-5 | Multiple related components |
| Large | 6+ | Cross-cutting concerns, architecture impact |
Scale affects skill priority:
- Larger scale → process/documentation skills more important
- Smaller scale → implementation skills more focused
3. Identify Task Type
| Type | Characteristics | Key Skills |
|---|---|---|
| Implementation | New code, features | coding-principles, testing-principles |
| Fix | Bug resolution | ai-development-guide, testing-principles |
| Refactoring | Structure improvement | coding-principles, ai-development-guide |
| Design | Architecture decisions | documentation-criteria, implementation-approach |
| Quality | Testing, review | testing-principles, integration-e2e-testing |
4. Tag-Based Skill Matching
Extract relevant tags from task description and match against skills-index.yaml:
Task: "Implement user authentication with tests"
Extracted tags: [implementation, testing, security]
Matched skills:
- coding-principles (implementation, security)
- testing-principles (testing)
- ai-development-guide (implementation)
5. Implicit Relationships
Consider hidden dependencies:
| Task Involves | Also Include |
|---|---|
| Error handling | debugging, testing |
| New features | design, implementation, documentation |
| Performance | profiling, optimization, testing |
| Frontend | typescript-rules, typescript-testing |
| API/Integration | integration-e2e-testing |
Output Format
Return structured analysis with skill metadata from skills-index.yaml:
taskAnalysis:
essence: <string> # Fundamental purpose identified
type: <implementation|fix|refactoring|design|quality>
scale: <small|medium|large>
estimatedFiles: <number>
tags: [<string>, ...] # Extracted from task description
selectedSkills:
- skill: <skill-name> # From skills-index.yaml
priority: <high|medium|low>
reason: <string> # Why this skill was selected
# Pass through metadata from skills-index.yaml
tags: [...]
typical-use: <string>
size: <small|medium|large>
sections: [...] # All sections from yaml, unfiltered
Note: Section selection (choosing which sections are relevant) is done after reading the actual SKILL.md files.
Skill Selection Priority
- Essential - Directly related to task type
- Quality - Testing and quality assurance
- Process - Workflow and documentation
- Supplementary - Reference and best practices
Metacognitive Question Design
Generate 3-5 questions according to task nature:
| Task Type | Question Focus |
|---|---|
| Implementation | Design validity, edge cases, performance |
| Fix | Root cause (5 Whys), impact scope, regression testing |
| Refactoring | Current problems, target state, phased plan |
| Design | Requirement clarity, future extensibility, trade-offs |
Warning Patterns
Detect and flag these patterns:
| Pattern | Warning | Mitigation |
|---|---|---|
| Large change at once | High risk | Split into phases |
| Implementation without tests | Quality risk | Follow TDD |
| Immediate fix on error | Root cause missed | Pause, analyze |
| Coding without plan | Scope creep | Plan first |