plan

Create phased implementation plans with dependencies, risks, and success criteria.

24|5|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Luohaothu/everything-codex --skill plan-luohaothu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Luohaothu/everything-codex/tree/main/skills/plan
Command: npx skills add https://github.com/Luohaothu/everything-codex --skill plan-luohaothu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex software features, architecture changes, and refactors can be error-prone and time-consuming without a structured, repeatable process that reduces risk and clarifies milestones.

Core Features & Use Cases

  • Structured requirements analysis and risk assessment to inform phased delivery.
  • Phase-based implementation planning with explicit steps, dependencies, and success criteria.
  • Reusable templates for architecture decisions and planning across projects.

Quick Start

Create a detailed implementation plan for a complex feature request.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan complex software features before coding?

Planning complex software features involves identifying requirements, risks, and dependencies to create an actionable implementation plan. This structured approach ensures phased delivery by breaking down architecture changes into explicit steps with clear success criteria and milestones.

What is the best way to structure requirements analysis for a major refactor?

Requirements analysis for a major refactor should apply a structured, repeatable process that assesses risks and identifies dependencies. This generates planning artifacts containing phase-based steps and success criteria to guide safe, phased delivery across software projects.

Does architecture planning work for both new features and system refactors?

Architecture planning works for both new features and system refactors by identifying risks and dependencies upfront. It creates reusable templates for architecture decisions, providing phase-based implementation steps and milestones that ensure safe delivery regardless of project scope.

How do I create an actionable implementation plan with clear milestones?

Creating an actionable implementation plan with clear milestones requires identifying dependencies and risks to define phase-based steps. Each phase includes explicit actions and success criteria, transforming complex feature requests into structured, safe delivery artifacts.

When do I need risk assessment for phased delivery in software engineering?

Risk assessment for phased delivery is needed when planning complex features, architecture changes, or refactors. It identifies potential blockers and dependencies early, ensuring the resulting implementation plan includes safe, phase-based steps with clear success criteria.

Can I use a phased delivery plan to manage dependencies across software projects?

A phased delivery plan manages dependencies across software projects by identifying and mapping them during the requirements analysis phase. This creates a structured implementation plan where phase-based steps explicitly account for dependencies, ensuring safe execution and clear milestones.