plan

Facilitate multi-phase strategic planning workflows with requirement analysis, design review, and documentation.

1|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/Cheggin/skill-chain --skill plan-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Cheggin/skill-chain/tree/main/skills/plan
Command: npx skills add https://github.com/Cheggin/skill-chain --skill plan-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the complex process of creating comprehensive work plans, helping users structure requirements, evaluate options, and ensure quality beforehand.

Core Features & Use Cases

  • Structured Planning: Guides users through requirement gathering, alternative analysis, and quality checks.
  • Collaborative Review: Supports iterative feedback with Architect and Critic reviews, including structured summaries and ADR documentation.
  • Use Case: For project managers or engineers needing to craft detailed technical plans, this Skill facilitates disciplined analysis, risk mitigation, and decision recording.

Quick Start

Ask the AI to help create a detailed project or feature plan, such as "Plan the architecture for a new microservice," and it will guide you through the entire process.

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 structure requirements and evaluate architecture options for a new software project?

Strategic planning for software projects involves guiding users through requirement gathering, alternative analysis, and quality checks to ensure clear decisions and risk mitigation. This approach uses structured prompts and review cycles to evaluate options comprehensively before implementation begins.

How do I create a comprehensive technical plan that includes risk management and architecture review?

Creating a technical plan with risk management involves multi-phase workflows that integrate requirement analysis, collaborative Architect and Critic reviews, and ADR documentation. This ensures disciplined analysis, iterative feedback, and detailed decision recording aligned with your project goals.

Can I use Markdown and YAML to document strategic decisions and project workflows?

Yes, you can leverage YAML and Markdown to facilitate structured strategic planning workflows and generate detailed documentation. These formats support requirement analysis and quality evaluation, ensuring that decisions and project goals are recorded clearly and aligned.

Does this interactive planning approach support iterative feedback and comparative analysis for microservice architecture?

Yes, interactive planning supports iterative feedback through structured review cycles and comparative analysis for microservice architecture. It leverages external agents for collaboration to conduct design reviews, evaluate quality, and mitigate risks throughout the planning process.

When do I need to use ADR documentation and structured summaries in a project planning workflow?

You need ADR documentation and structured summaries during collaborative review phases of project planning to record clear decisions and capture iterative feedback. This ensures that risk management and quality evaluation outcomes are detailed and aligned with project goals.