plan

Create structured multi-phase plans with frontmatter metadata and phase files.

Updated Feb 27, 2026

Search Tags:#planning #architecture #roadmap #phase #team-alignment #planning-tools

Ready to run

npx skills add https://github.com/haidonglethqb/CloudSchool --skill plan-haidonglethqb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/haidonglethqb/CloudSchool/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/haidonglethqb/CloudSchool --skill plan-haidonglethqb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning and documenting implementation roadmaps, system designs, and phased execution to align teams and ensure traceable delivery across projects.

Core Features & Use Cases

Create structured, multi-phase plans with frontmatter metadata and phase files.
Analyze codebases and architectures to design robust roadmaps for feature development and refactors.
Generate execution-ready plans that feed planning tools, red-team reviews, and validation workflows.

Quick Start

Create a new plan by writing plan.md and at least three phase files (phase-01-...), then hydrate tasks and prepare for review.

Frequently Asked Questions about plan

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

FAQPage Schema

What is the best way to create a multi-phase roadmap for a large system refactor?▼

Planning a feature development roadmap requires analyzing codebases and architectures to design structured, multi-phase plans. You need to generate execution-ready plan outputs with frontmatter metadata and phase files to guide engineering teams and ensure traceable delivery.

How do I structure execution-ready plans to align engineering and product teams?▼

You align engineering and product teams by generating structured phase files with frontmatter metadata that define executable plan outputs. This multi-phase structure ensures traceable delivery and drives execution, review, and validation workflows across software engineering and design processes.

Can I use structured phase files for new platform initiatives and codebase analysis?▼

Structured phase files support new platform initiatives by analyzing architectures and generating robust roadmaps with frontmatter metadata. These execution-ready plan outputs drive review, validation workflows, and traceable delivery across product-management, software engineering, and design processes.

Why does my roadmap plan require frontmatter metadata and separate phase files?▼

Roadmap plans require frontmatter metadata and separate phase files to ensure execution readiness and traceable delivery across multi-phase projects. This structured documentation aligns engineering and product teams while feeding directly into planning tools, red-team reviews, and validation workflows.

What are the limitations of using static documentation for system design roadmaps?▼

Static documentation lacks the structured frontmatter metadata and executable phase files needed for traceable delivery. Without execution-ready plan outputs, your system design roadmaps cannot effectively drive validation workflows, red-team reviews, and team alignment across large refactors or new platform initiatives.