planning

Plan software implementations, system architecture, and technical roadmaps.

Updated Feb 14, 2026

Search Tags:#design #planning #architecture #implementation #roadmap #technical strategy

Ready to run

npx skills add https://github.com/toanalien/ezdevsecops --skill planning-toanalien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/toanalien/ezdevsecops/tree/main/.opencode/skills/planning
Command: npx skills add https://github.com/toanalien/ezdevsecops --skill planning-toanalien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to planning software implementations, designing architectures, and creating technical roadmaps, ensuring clarity and actionable steps.

Core Features & Use Cases

Feature Planning: Break down new feature requirements into manageable phases.
System Design: Architect complex systems with detailed component interactions.
Roadmap Creation: Develop phased technical roadmaps with clear deliverables.
Use Case: When starting a new large feature, use this skill to generate a detailed plan outlining research, design, implementation phases, and task breakdowns.

Quick Start

Use the planning skill to create a new implementation plan for the 'user authentication' feature.

Frequently Asked Questions about planning

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

FAQPage Schema

What is software architecture design and when do I need a technical roadmap?▼

Software architecture design structures complex systems into detailed components, while a technical roadmap phases deliverables. You need these when starting large features to ensure clear research, design, and actionable implementation steps.

How do I create an implementation plan for a new software feature?▼

To create an implementation plan, break down feature requirements into manageable phases. This involves conducting research, analyzing the codebase, designing solutions, and organizing detailed task breakdowns adhering to YAGNI, KISS, and DRY principles.

What's the best way to break down complex system design into manageable phases?▼

The best way to break down complex system design is using a structured planning approach. This guides you through research, codebase analysis, solution architecture, and detailed phase documentation to ensure clarity and actionable steps.

Can I use this approach for both feature planning and overall technical strategy?▼

Yes, you can use this approach for both feature planning and overall technical strategy. It supports breaking down new feature requirements, architecting complex systems, and developing phased technical roadmaps with clear deliverables.

What principles should I follow when organizing an implementation strategy?▼

When organizing an implementation strategy, you should follow YAGNI, KISS, and DRY principles. These ensure your solution architecture and phase documentation remain focused, simple, and free of unnecessary duplication.

How does codebase analysis fit into the technical planning process?▼

Codebase analysis fits into technical planning by informing the solution design phase. It helps you understand existing structures before creating a detailed implementation plan, ensuring new architecture integrates seamlessly.