Maintains a record of implementation and handover plans in docs/plan/ for traceability.
Install
mkdir -p .claude/skills/plan-rain-kl && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17540" && unzip -o skill.zip -d .claude/skills/plan-rain-kl && rm skill.zipInstalls to .claude/skills/plan-rain-kl
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.
项目级技能：规定在开启新方案、新计划或进行任务交接时，必须将计划落库到 docs/plan 文件夹中并使用对应模板。Key capabilities
- →Document new feature development plans
- →Create handover plans for unfinished tasks
- →Standardize plan documentation using templates
- →Store plans in a designated directory
- →Ensure plans are not exposed externally
How it works
It requires the user to select a plan type (implementation or handover), read the corresponding template, and save the plan as a Markdown file in `docs/plan/` with a specific naming convention. It also enforces that these documents remain internal.
Inputs & outputs
When to use plan
- →Initiating a major feature build
- →Documenting technical debt refactorings
- →Handing off unfinished work to another developer
About this skill
Plan & Handover Skill
当你在当前项目中被要求“开启一个新的方案”、“制定开发计划”或者准备“任务交接（Handover）”时，你必须遵循本技能的工作流，将计划或方案落库到 docs/plan/ 目录下。
[!IMPORTANT] 什么时候应当创建实现计划？
- 必须创建的场景：新功能开发、涉及多组件的重大架构重构、引入新基础设施依赖，以及存在显著设计决策冲突的中大型、复杂需求。
- 绝对不要创建的场景：改个包名、挪个文件、重命名函数、小修小改修复 Bug 等轻量级、简单的局部重构。对于此类改动，应当直接完成并运行单元测试通过后交付，禁止制造冗余的计划文档。
执行工作流 (Workflow)
1. 确定计划类型
- 新特性/技术实现计划：如果你要开发新功能或进行重大重构，你需要创建实现计划。
- AI 任务交接计划：如果当前任务尚未完成但需要记录进度留作以后或其他 AI 代理接手，你需要创建交接计划。
2. 读取对应模板
在创建计划文档前，必须读取对应的模板内容，并严格按照模板的骨架进行填充：
- 实现计划模板：
docs/plan/implementation-plan-template.md - 接手计划模板：
docs/plan/handover-plan-template.md
3. 落库与命名规范
在 docs/plan/ 目录下创建新的 Markdown 文件进行保存：
- 实现计划命名格式：
docs/plan/YYYYMMDD-[feature-name].md(例如：20260605-uptime-kuma-sync.md) - 接手计划命名格式：
docs/plan/handover-[task-name].md(例如：handover-waf-ip-group.md)
4. 隔离约束 (极其重要)
docs/plan/ 目录下的文档仅限内部开发和 AI 代理同步使用。
- 绝对禁止将新创建的 plan 文档加入到项目的官方导航配置（如
docs/config.ts的nav或sidebar导航条中）。 - 绝对禁止通过任何方式将其暴露给文档渲染框架（如 VitePress）对外渲染。
后续动作
落库完成后，向用户报告计划已生成在 docs/plan/ 目录下，并列出文档的核心要点或待决策项（如有），等待用户 Review 或批准后即可推进下一步。
When not to use it
- →When making minor code changes like renaming a package or fixing a small bug
- →When the task is a lightweight, simple local refactor
- →When the plan document is intended for external exposure
Limitations
- →Plan documents must be stored in `docs/plan/`
- →Plan documents must not be exposed to external rendering frameworks
- →Requires strict adherence to naming conventions
How it compares
This skill formalizes the planning and handover process by enforcing template usage and specific storage locations, ensuring consistency and preventing external exposure of internal plans.
Compared to similar skills
plan side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| plan (this skill) | 0 | 1mo | No flags | Beginner |
| pmbok-project-management | 38 | 8mo | No flags | Intermediate |
| project-planner | 32 | 9mo | Review | Intermediate |
| spec-kit-workflow | 11 | 7mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Rain-kl
View all by Rain-kl →You might also like
pmbok-project-management
jgtolentino
Comprehensive PMP/PMBOK project management methodologies and best practices. Use this skill when users need guidance on project management processes, templates, knowledge areas, process groups, tools, techniques, or certification preparation. Covers all 10 PMBOK Knowledge Areas and 5 Process Groups with practical templates, frameworks, and industry-standard approaches. Includes risk management, stakeholder engagement, schedule management, cost control, quality assurance, and resource planning.
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.
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).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
planning-agent
parcadei
Planning agent that creates implementation plans and handoffs from conversation context
pdd
mikeyobrien
Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.