planning

Develop technical implementation plans and system designs from codebase analysis.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Hoang130203/Emgu_CV_automation --skill planning-hoang130203
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/Hoang130203/Emgu_CV_automation/tree/main/.opencode/skills/planning
Command: npx skills add https://github.com/Hoang130203/Emgu_CV_automation --skill planning-hoang130203

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to planning complex software projects, from initial feature ideation to detailed implementation roadmaps, ensuring clarity and alignment.

Core Features & Use Cases

  • Feature Planning: Define scope, requirements, and phases for new features.
  • System Design: Architect technical solutions, considering trade-offs and best practices.
  • Roadmap Creation: Break down large initiatives into actionable steps with timelines.
  • Use Case: When starting a new microservice, use this Skill to outline its architecture, define API contracts, plan database schema, and detail the implementation phases.

Quick Start

Use the planning skill to create a detailed implementation plan for a new user authentication module.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a technical implementation plan for a new microservice?

To create a technical implementation plan, analyze the existing codebase and documentation to define architecture, API contracts, database schemas, and implementation phases while adhering to YAGNI, KISS, and DRY principles.

What is solution architecture design and when do I need it?

Solution architecture design is the process of defining technical structures, trade-offs, and best practices for software systems. You need it when starting complex features or new microservices to ensure clarity and alignment.

Does this approach to feature planning work without existing code?

No, this feature planning approach requires detailed analysis of existing code and documentation to propose optimal strategies. It relies on evaluating current systems to define scope, requirements, and implementation phases accurately.

How do I document system designs for complex software projects?

You document system designs by conducting research and analyzing codebases to architect technical solutions. This process ensures you capture trade-offs, best practices, and phase documentation for comprehensive project alignment.

What are the limitations of using automated planning for system design?

The limitation of automated planning is that it cannot operate without context; it requires detailed analysis of existing code and documentation. It proposes strategies based strictly on provided inputs rather than generating architecture from scratch.