AgentSkillsCN

planning

技术实施规划和架构设计。功能：特性规划、系统架构、技术评估、实施路线图、需求分解、权衡分析、代码库分析、解决方案设计。动作：规划、架构、设计、评估、分解技术解决方案。关键词：实施计划、技术设计、架构、系统设计、路线图、需求分析、权衡、技术评估、特性规划、解决方案设计、可扩展性、安全性、可维护性、冲刺规划、任务分解。适用场景：规划新特性、设计系统架构、评估技术方案、创建实施路线图、分解复杂需求、评估技术权衡。

SKILL.md
--- frontmatter
name: planning
description: "Technical implementation planning and architecture design. Capabilities: feature planning, system architecture, technical evaluation, implementation roadmaps, requirement breakdown, trade-off analysis, codebase analysis, solution design. Actions: plan, architect, design, evaluate, breakdown technical solutions. Keywords: implementation plan, technical design, architecture, system design, roadmap, requirements analysis, trade-offs, technical evaluation, feature planning, solution design, scalability, security, maintainability, sprint planning, task breakdown. Use when: planning new features, designing system architecture, evaluating technical approaches, creating implementation roadmaps, breaking down complex requirements, assessing technical trade-offs."
license: MIT

Planning

Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.

When to Use

Use this skill when:

  • •Planning new feature implementations
  • •Architecting system designs
  • •Evaluating technical approaches
  • •Creating implementation roadmaps
  • •Breaking down complex requirements
  • •Assessing technical trade-offs

Core Responsibilities & Rules

Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.

1. Research & Analysis

Load: references/research-phase.md Skip if: Provided with researcher reports

2. Codebase Understanding

Load: references/codebase-understanding.md Skip if: Provided with scout reports

3. Solution Design

Load: references/solution-design.md

4. Plan Creation & Organization

Load: references/plan-organization.md

5. Task Breakdown & Output Standards

Load: references/output-standards.md

Workflow Process

  1. •Initial Analysis → Read codebase docs, understand context
  2. •Research Phase → Spawn researchers, investigate approaches
  3. •Synthesis → Analyze reports, identify optimal solution
  4. •Design Phase → Create architecture, implementation design
  5. •Plan Documentation → Write comprehensive plan
  6. •Review & Refine → Ensure completeness, clarity, actionability

Output Requirements

  • •DO NOT implement code - only create plans
  • •Respond with plan file path and summary
  • •Ensure self-contained plans with necessary context
  • •Include code snippets/pseudocode when clarifying
  • •Provide multiple options with trade-offs when appropriate
  • •Fully respect the ./docs/development-rules.md file.

Plan Directory Structure

code
plans/
└── YYYYMMDD-HHmm-plan-name/
    ├── research/
    │   ├── researcher-XX-report.md
    │   └── ...
    ├── reports/
    │   ├── XX-report.md
    │   └── ...
    ├── scout/
    │   ├── scout-XX-report.md
    │   └── ...
    ├── plan.md
    ├── phase-XX-phase-name-here.md
    └── ...

Quality Standards

  • •Be thorough and specific
  • •Consider long-term maintainability
  • •Research thoroughly when uncertain
  • •Address security and performance concerns
  • •Make plans detailed enough for junior developers
  • •Validate against existing codebase patterns

Remember: Plan quality determines implementation success. Be comprehensive and consider all solution aspects.