Coordinates complex tasks using a single plan.md file. Ensures clear requirements, design, and verification before execution.
Install
mkdir -p .claude/skills/plan-luckymaomi && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18272" && unzip -o skill.zip -d .claude/skills/plan-luckymaomi && rm skill.zipInstalls to .claude/skills/plan-luckymaomi
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
用于写作和执行单文件 plan.md。适用于中大型开发、跨模块重构、生产级验收、恢复演练、架构硬化、评测闭环，以及任何不能靠一次小补丁完成的任务；要求把 plan.md 写成需求、事实、失败测试、目标、设计、任务、验证和收口合一的规格驱动执行合同。Key capabilities
- →Write a demand document
- →Document current facts
- →Define failure tests
- →Outline project goals
- →Specify design details
- →List implementation tasks
How it works
The skill guides the user through creating a `plan.md` document by following a predefined sequence of sections, ensuring all aspects of a complex task are covered.
Inputs & outputs
When to use plan
- →Executing cross-module refactoring
- →Planning complex feature implementation
- →Performing system architecture hardening
About this skill
Plan
plan.md 是单文件规格驱动执行合同。
它同时承担需求文档、当前事实、失败测试、目标合同、设计合同、实施任务、验证计划和收口记录。
没有完整 plan.md，不做大改。
执行中发现事实推翻计划，先更新 plan.md，再继续。
写作顺序
必须按这个顺序写 plan.md：
- 需求文档。
- 当前事实。
- 失败测试。
- 目标。
- 不做范围。
- 设计。
- 实施任务。
- 验证计划。
- 收口。
执行规则
- 写完计划，再动手。
- checklist 必须随进度更新。
- 新事实推翻计划，先改计划，再继续。
- 不用口头解释替代计划更新。
- 不偷偷偏离计划。
- 不把旧能力、旧状态、旧数据写成当前产品事实。
- 不为了简短牺牲边界、失败测试和验证。
- 提出一个方向后，要把 research、设计、实现、测试、文档同步、验证和收口做成完整闭环。
- 不把方向拆成反复让 owner 推动的小步。除非遇到客观阻塞，否则同一方向做到可交付、可验证、可长期保留。
标准模板
# [任务名] Plan
## 1. 需求文档
## 2. 当前事实
## 3. 失败测试
## 4. 目标
## 5. 不做范围
## 6. 设计
## 7. 实施任务
## 8. 验证计划
## 9. 收口
When not to use it
- →When the task can be completed with a small patch
- →When the task does not require a detailed plan.md
- →When the user does not want to follow a structured planning process
Limitations
- →Requires adherence to a specific `plan.md` structure
- →Does not allow for deviation from the plan without updating the document
How it compares
This workflow enforces a structured, specification-driven approach to planning complex tasks, unlike ad-hoc planning or informal documentation.
Compared to similar skills
plan side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| plan (this skill) | 0 | 27d | No flags | Intermediate |
| create-plan | 36 | 7mo | Review | Beginner |
| project-planner | 32 | 9mo | Review | Intermediate |
| system-design | 19 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.