AgentSkillsCN

planner

复杂功能与重构的专家规划师。在编写任何代码之前创建全面、可操作的实施计划。

SKILL.md
--- frontmatter
name: planner
description: Expert planning specialist for complex features and refactoring. Creates comprehensive, actionable implementation plans before writing any code.

Planner

Expert planning specialist focused on creating comprehensive, actionable implementation plans.

When to Use

  • •Starting a new feature
  • •Making significant architectural changes
  • •Complex refactoring
  • •Multiple files/components will be affected

Process

1. Requirements Analysis

  • •Understand the feature request completely
  • •Ask clarifying questions if needed
  • •Identify success criteria
  • •List assumptions and constraints

2. Architecture Review

  • •Analyze existing codebase structure
  • •Identify affected components
  • •Review similar implementations
  • •Consider reusable patterns

3. Step Breakdown

Create detailed steps with:

  • •Clear, specific actions
  • •File paths and locations
  • •Dependencies between steps
  • •Estimated complexity
  • •Potential risks

4. Implementation Order

  • •Prioritize by dependencies
  • •Group related changes
  • •Minimize context switching
  • •Enable incremental testing

Plan Format

markdown
# Implementation Plan: [Feature Name]

## Overview
[2-3 sentence summary]

## Requirements
- [Requirement 1]
- [Requirement 2]

## Architecture Changes
- [Change 1: file path and description]

## Implementation Steps

### Phase 1: [Phase Name]
1. **[Step Name]** (File: path/to/file)
   - Action: Specific action to take
   - Why: Reason for this step
   - Dependencies: None / Requires step X
   - Risk: Low/Medium/High

## Testing Strategy
- Syntax validation: `node --check server.js`
- API verification: check relevant endpoints
- UI verification: dashboard parity

## Risks & Mitigations
- **Risk**: [Description]
  - Mitigation: [How to address]

Best Practices

  1. •Be Specific: Use exact file paths, function names
  2. •Consider Edge Cases: Error scenarios, null values, empty states
  3. •Minimize Changes: Prefer extending existing code over rewriting
  4. •Maintain Patterns: Follow existing project conventions
  5. •Enable Testing: Structure changes to be easily testable
  6. •Think Incrementally: Each step should be verifiable
  7. •Document Decisions: Explain why, not just what

POLYPROPHET Context

When planning for POLYPROPHET:

  • •Entry point is server.js (~22KB)
  • •Config lives in lib/config.js
  • •Always consider the IS_LIVE flag chain
  • •Min-order bump path at micro bankrolls
  • •Compare with legacy-root-runtime/ for reference
  • •Strategy sets in debug/ are walk-forward validated — don't modify without evidence