TA

task-analyzer

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.zip

Installs 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.
136 chars✓ has a “when” trigger
Beginner

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

You give it
Task description
You get back
Structured analysis with task essence, type, scale, tags, selected skills, and metacognitive questions

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 WorkFundamental 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.

ScaleDecision burden
SmallOne coherent outcome, one evident repository-supported implementation within one responsibility boundary, and no unresolved durable choice
MediumOne coherent outcome that coordinates a boundary or contains a potentially durable choice
LargeMultiple 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

TypeCharacteristicsKey Skills
implementationNew code or user-visible behaviorcoding-standards, typescript-testing
fixDefect or regression resolutioncoding-standards, typescript-testing
refactoringBehavior-preserving structure improvementcoding-standards, implementation-approach
designArchitecture or contract decisionsdocumentation-criteria, implementation-approach
qualityTesting, review, verificationtypescript-testing, integration-e2e-testing
documentationPRD, ADR, Design Doc, UI Spec, plan, or instruction contentdocumentation-criteria
investigationEvidence gathering without implementationproject-context plus the domain skill selected from the index
migrationData, schema, API, dependency, or runtime transitionimplementation-approach, documentation-criteria
operationsEnvironment, deployment, or runtime operationtechnical-spec plus the domain skill selected from the index
securitySecurity design or reviewcoding-standards plus the implementation-domain skill
skillSkill creation, prompt-quality review, or skill metadata changeskill-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 InvolvesAlso Include
Error handlingdebugging, testing
New featuresdesign, implementation, documentation
Performanceprofiling, optimization, testing
Frontendtypescript-rules, typescript-testing
API/Integrationintegration-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

  1. Intent gate: Proceed to scale estimation when essence, primary type, and any secondaryTypes are recorded. If the requested outcome is ambiguous, record the exact outcome decision required.
  2. Scale gate: Proceed to skill matching when the outcome and responsibility-boundary evidence is sufficient for Structural Scale and scaleRationale names the deciding axis.
  3. 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

  1. Essential - Directly related to task type
  2. Quality - Testing and quality assurance
  3. Process - Workflow and documentation
  4. 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 TypeQuestion Focus
ImplementationDesign validity, edge cases, performance
FixRoot cause (5 Whys), impact scope, regression testing
RefactoringCurrent problems, target state, phased plan
DesignRequirement clarity, future extensibility, trade-offs
DocumentationAudience, source of truth, approval/consumer contract
InvestigationClaim to resolve, evidence boundary, stopping condition
MigrationCompatibility window, data/contract transition, rollback
OperationsTarget environment, authorization boundary, recovery evidence
SecurityTrust boundary, protected asset, threat/acceptance source
SkillTriggering intent, standalone context, output consumer

Warning Patterns

Detect and flag these patterns:

PatternWarningMitigation
One step contains multiple independently verifiable outcomesTransition and rollback riskSplit at observable verification boundaries
A behavior change has no test or named runnable verificationRegression evidence is missingAdd the cheapest check that observes the changed contract
A proposed fix has no observed causal link to the failureRoot cause remains inferredRecord reproduction evidence and the first causal boundary before selecting the fix
Medium/Large implementation lacks its scale-required planning artifactScope and dependency contract is missingCreate 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.

SkillInstallsUpdatedSafetyDifficulty
task-analyzer (this skill)72moNo flagsBeginner
product-manager-toolkit327moReviewBeginner
micro-saas-launcher66moNo flagsIntermediate
game-changing-features46moNo flagsAdvanced

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.

3280

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.

655

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'.

443

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.

1027

challenge

alirezarezvani

/em -challenge — Pre-Mortem Plan Analysis

27

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.

18

Search skills

Search the agent skills registry