AgentSkillsCN

pm-organization-task-research

PM 任务分配的专业代码库研究专家。在分配任务之前，主动了解现有模式、依赖关系与实施路径，以便更好地把握全局。

SKILL.md
--- frontmatter
name: pm-organization-task-research
description: Codebase research specialist for PM task assignment. Use proactively before assigning tasks to understand existing patterns, dependencies, and implementation approaches.
user-invocable: true
category: organization

PM Task Research

"Research before assignment - prevent misallocation and blockers."

Explore the codebase and return structured summaries for task assignment. This helps ensure tasks are assigned to the right agent with accurate complexity estimates.

When to Use

Use proactively before assigning tasks to understand:

  • •Existing patterns in the codebase
  • •Files/components the task will touch
  • •Potential blockers or dependencies
  • •Which agent should handle the task
  • •Complexity estimate

Research Process

  1. •Use Grep to find related implementations
  2. •Use Read to examine relevant files
  3. •Use Glob to find related components
  4. •Provide a structured summary (not raw exploration)

What to Research

For Each Task

  1. •Existing Patterns: What similar implementations exist?
  2. •Dependencies: What files/components will this task touch?
  3. •Blockers: Are there any blocking issues or missing dependencies?
  4. •Agent Fit: Should this go to Developer or Tech Artist?
  5. •Complexity Estimate: Micro/Simple/Medium/Complex based on codebase state

Agent Selection Guide

CategoryDefault AgentWhen to Reassign
architecturaldeveloperIf visual-heavy → techartist
functionaldeveloperIf shader/VFX work → techartist
integrationdeveloper-
visualtechartistIf logic-heavy → developer
shadertechartist-
polishtechartistIf functional changes → developer

Complexity Estimation

LevelCriteriaExample
MicroSingle line change, config updateFix typo, change color value
SimpleSingle file, well-defined patternAdd utility function, simple component
Medium2-5 files, some coordinationAdd feature to existing system
Complex5+ files, new patterns, architectureNew system, refactoring, multiplayer

Output Format

markdown
## Task Research: {TASK_ID}

### Task Summary
- **Title:** {task title}
- **Category:** {architectural|functional|visual|shader|polish|integration}
- **Description:** {brief description}

### Existing Patterns
- Pattern 1: {location} - {brief description}
- Pattern 2: {location} - {brief description}

### Dependencies
- {file/path} - {reason for dependency}
- {file/path} - {reason for dependency}

### Files That Will Be Modified
- {file/path} - {what needs to change}
- {file/path} - {what needs to change}

### Blockers
- (if none, state "No blockers identified")
- (if blockers exist, list them with severity)

### Recommended Agent
- {developer|techartist} - {justification}

### Complexity Estimate
- {Micro|Simple|Medium|Complex} - {justification}

### Implementation Notes
- Any relevant notes for the implementing agent
- Potential gotchas or areas requiring extra care

Important

  • •Keep analysis concise and actionable
  • •Don't return verbose file contents
  • •Focus on what the PM needs to know for assignment
  • •If you find critical issues, flag them prominently
  • •Always identify which agent should handle the task
  • •Be realistic about complexity estimates

See Also