planning-phase

Generate implementation plans with code reuse and project documentation alignment.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill planning-phase-sjdjdiejdrirhdkjej
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-phase
Source: https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor/tree/main/.claude/skills/planning-phase
Command: npx skills add https://github.com/Sjdjdiejdrirhdkjej/Claude-code-conductor --skill planning-phase-sjdjdiejdrirhdkjej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the planning phase to generate implementation plans that maximize code reuse and align with project documentation.

Core Features & Use Cases

  • Load and synthesize constraints from docs/project
  • Identify 5-15 reuse opportunities by scanning codebase
  • Design architecture with components, layers, and patterns
  • Plan data model/entities and migrations
  • Define API contracts (OpenAPI) where applicable
  • Plan testing strategy and coverage
  • Produce a realistic complexity estimate (20-30 tasks)

Quick Start

Step-by-step planning workflow: load docs, search for reuse, design architecture, plan data model, define API contracts, plan testing, estimate complexity.

Frequently Asked Questions about planning-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an implementation plan that maximizes code reuse?▼

Designing system architecture involves loading project constraints, identifying 5-15 reuse opportunities, defining components and layers, planning data models, and defining OpenAPI contracts to structure the system effectively.

What's the best way to plan API contracts and data models for a new feature?▼

Planning API contracts and data models involves synthesizing project constraints, designing system architecture layers, defining OpenAPI specifications, and planning entity migrations to maximize code reuse and alignment.

How do I estimate complexity for a feature implementation plan?▼

To estimate complexity for an implementation plan, break the work into 20-30 realistic tasks after architecture design, data model planning, API contract definition, and testing strategy formulation are complete.

Does this planning workflow require existing project documentation?▼

Yes, this planning workflow requires existing project documentation because it loads and synthesizes constraints from the docs/project directory to align the implementation plan and architecture with project standards.

When should I not use a reuse-first architecture planning approach?▼

Avoid a reuse-first architecture planning approach before the specification phase completes, as this process depends on finalized specifications to orchestrate architecture design, API contract definitions, and complexity estimation.