跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

task-analyzer

Classifies task intent, change risk, and execution scale, then selects skills from the project skills index. Use when starting work, routing a task, estimating scope, or selecting skills.

shinpr · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add shinpr/ai-coding-project-boilerplate --skill task-analyzer

技能说明


name: task-analyzer description: Classifies task intent, change risk, and execution scale, then selects skills from the project skills index. Use when starting work, routing a task, estimating scope, or selecting skills.

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.

Skil

阅读完整来源 ↗