Analyzes tasks to determine the best approach and skill set.
Install
mkdir -p .claude/skills/task-analyzer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/379" && unzip -o skill.zip -d .claude/skills/task-analyzer && rm skill.zipInstalls to .claude/skills/task-analyzer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Analyzes task essence and selects appropriate skills. Returns scale estimates and metadata. Use when starting tasks or selecting skills.Key capabilities
- →Identify the fundamental purpose of a task
- →Estimate the scale of a task (small, medium, large)
- →Identify the type of a task (implementation, fix, refactoring, design, quality)
- →Match relevant skills based on task tags
- →Generate metacognitive questions for task analysis
How it works
The skill analyzes a task by identifying its fundamental purpose, estimating its scale, determining its type, and matching relevant skills from a predefined index.
Inputs & outputs
When to use task-analyzer
- →Analyze a task to determine its technical scale
- →Identify the fundamental purpose of a feature request
- →Select the right skills for a complex refactoring task
- →Estimate the impact of a code change
About this skill
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 Structural Scale
Classify decision burden from the intended outcomes and responsibility boundaries. File count is supporting evidence only.
| Scale | Decision burden |
|---|---|
| Small | One coherent outcome, one evident repository-supported implementation within one responsibility boundary, and no unresolved durable choice |
| Medium | One coherent outcome that coordinates a boundary or contains a potentially durable choice |
| Large | Multiple independently valuable outcomes that require separate design decisions |
A cross-layer implementation can remain Medium when it serves one coherent outcome. A decision point passing both documentation-criteria ADR filters raises the scale to Medium at minimum. Record the evidence that established the outcome and boundary classification in scaleRationale.
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 or user-visible behavior | coding-standards, typescript-testing |
| fix | Defect or regression resolution | coding-standards, typescript-testing |
| refactoring | Behavior-preserving structure improvement | coding-standards, implementation-approach |
| design | Architecture or contract decisions | documentation-criteria, implementation-approach |
| quality | Testing, review, verification | typescript-testing, integration-e2e-testing |
| documentation | PRD, ADR, Design Doc, UI Spec, plan, or instruction content | documentation-criteria |
| investigation | Evidence gathering without implementation | project-context plus the domain skill selected from the index |
| migration | Data, schema, API, dependency, or runtime transition | implementation-approach, documentation-criteria |
| operations | Environment, deployment, or runtime operation | technical-spec plus the domain skill selected from the index |
| security | Security design or review | coding-standards plus the implementation-domain skill |
| skill | Skill creation, prompt-quality review, or skill metadata change | skill-optimization, llm-friendly-context |
When multiple types apply, return the primary type that owns the requested outcome and list the remaining values in secondaryTypes.
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-standards (implementation, security)
- typescript-testing (testing)
- typescript-rules (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|documentation|investigation|migration|operations|security|skill>
secondaryTypes: [<task-type>, ...]
scale: <small|medium|large>
estimatedFiles: <number or unknown> # Supporting evidence only
scaleRationale:
decidingAxis: <outcomes|responsibility-boundaries|durable-choice>
evidence: <string>
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 separately after reading the actual SKILL.md files.
Process Gates
- Intent gate: Proceed to scale estimation when
essence, primarytype, and anysecondaryTypesare recorded. If the requested outcome is ambiguous, record the exact outcome decision required. - Scale gate: Proceed to skill matching when the outcome and responsibility-boundary evidence is sufficient for Structural Scale and
scaleRationalenames the deciding axis. - Selection gate: Finalize when every selected skill exists in
skills-index.yaml, has a reason tied to the task, and its metadata is copied without invention.
When an unknown can change the outcome boundary, ADR qualification, or required workflow, request the exact repository evidence or user decision needed. An unknown file count alone does not block Structural Scale judgment.
Skill Selection Priority
- Essential - Directly related to task type
- Quality - Testing and quality assurance
- Process - Workflow and documentation
- Supplementary - Additional constraints or evidence directly tied to the task
Metacognitive Question Design
Generate only questions whose answers can change intent classification, scale, selected skills, a hard constraint, or verification. Return no question when repository evidence already resolves those decisions. For every question, record the decision it controls.
| 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 |
| Documentation | Audience, source of truth, approval/consumer contract |
| Investigation | Claim to resolve, evidence boundary, stopping condition |
| Migration | Compatibility window, data/contract transition, rollback |
| Operations | Target environment, authorization boundary, recovery evidence |
| Security | Trust boundary, protected asset, threat/acceptance source |
| Skill | Triggering intent, standalone context, output consumer |
Warning Patterns
Detect and flag these patterns:
| Pattern | Warning | Mitigation |
|---|---|---|
| One step contains multiple independently verifiable outcomes | Transition and rollback risk | Split at observable verification boundaries |
| A behavior change has no test or named runnable verification | Regression evidence is missing | Add the cheapest check that observes the changed contract |
| A proposed fix has no observed causal link to the failure | Root cause remains inferred | Record reproduction evidence and the first causal boundary before selecting the fix |
| Medium/Large implementation lacks its scale-required planning artifact | Scope and dependency contract is missing | Create the required artifact before implementation routing |
How it compares
This skill provides a structured, systematic approach to task analysis and skill selection, offering a guided process compared to an ad-hoc or intuitive method.
Compared to similar skills
task-analyzer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| task-analyzer (this skill) | 7 | 2mo | No flags | Beginner |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| micro-saas-launcher | 6 | 6mo | No flags | Intermediate |
| game-changing-features | 4 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
micro-saas-launcher
davila7
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
game-changing-features
davila7
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
job-search-strategist
proyecto26
Comprehensive job search strategy skill for analyzing job postings, discovering non-obvious insights, conducting conversational skills-matching interviews, identifying skill development needs, and creating creative, personalized application strategies. This skill should be used when users want help with job applications, career transitions, analyzing job opportunities, or developing targeted job search approaches that help them stand out from other candidates.
challenge
alirezarezvani
/em -challenge — Pre-Mortem Plan Analysis
risk-analysis
Prorise-cool
Risk analysis using risk registers, probability/impact matrices, and mitigation planning. Identifies, assesses, and manages project, business, and technical risks with structured response strategies.