planning-phase

marcusgoll 的头像作者 marcusgoll

"/plan阶段的标准操作程序。涵盖研究深度、代码重用检测、设计模式选择和架构规划。"

📖 中文导读:"/plan阶段的标准操作程序。涵盖研究深度、代码重用检测、设计模式选择和架构规划。" 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: planning-phase description: "Standard Operating Procedure for /plan phase. Covers research depth, code reuse detection, design pattern selection, and architecture planning." allowed-tools: Read, Grep, Glob, Bash

Planning Phase: Quick Reference

Purpose: Generate implementation plan with reuse analysis from spec.md, ensuring alignment with project documentation and maximizing code reuse.

Phase Overview

Inputs:

  • specs/NNN-slug/spec.md - Feature specification
  • docs/project/*.md - 8 project documentation files (if available)

Outputs:

  • specs/NNN-slug/plan.md - Implementation plan
  • specs/NNN-slug/research.md - Research findings and reuse opportunities

Expected duration: 1-3 hours


Quick Start Checklist

Before you begin:

  • Specification phase completed (spec.md exists)
  • Understand feature requirements
  • Project documentation available (or brownfield codebase)

Core workflow:

  1. ✅ Load Project Documentation - Read all 8 docs for constraints
  2. ✅ Research Code Reuse - Search before designing
  3. ✅ Design Architecture - Components, layers, patterns
  4. ✅ Plan Data Model - Entities, relationships, migrations
  5. ✅ Define API Contracts - Endpoints, schemas, validation
  6. ✅ Plan Testing Strategy - Unit, integration, E2E coverage
  7. ✅ Estimate Complexity - Task count prediction

Detailed Resources

🎯 Core Workflow

📊 Planning Artifacts

🔧 Estimation & Validation


Completion Criteria

Required:

  • plan.md created with architecture, components, API contracts
  • research.md created with reuse findings and project context
  • All 8 project docs read (or brownfield research complete)
  • Code reuse opportunities identified (5-15 expected)
  • Testing strategy defined (unit, integration, E2E)
  • Complexity estimated (20-30 tasks predicted)

Optional (if applicable):

  • Data model ERD created (Mermaid diagram)
  • API contracts in OpenAPI format
  • UI/UX flow diagram (for UI features)

Next Phase

After planning complete: → /tasks - Break down into concrete implementation tasks


See also: