create-plan
Create a persistent structured plan (plan.md, phases/, todo.md) when work needs multi-phase or multi-session coordination, durable tracking, or an explicitly requested plan.
DasDigitaleMomentum · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add DasDigitaleMomentum/opencode-processing-skills --skill create-plan技能说明
name: create-plan description: Create a persistent structured plan (plan.md, phases/, todo.md) when work needs multi-phase or multi-session coordination, durable tracking, or an explicitly requested plan. license: MIT compatibility: opencode metadata: category: planning phase: initial
Skill: Create Plan
What This Skill Does
Creates a complete plan with the artifacts required to execute work in phases. This documentation shall serve Agents and Humans when working in consecutive sessions with the project:
- Plan (
plans/<name>/plan.md) - Problem/context, target outcome, guiding decisions, requirements, DoD, phases overview - Phases (
plans/<name>/phases/phase-N.md) - Scope definition per phase (what/why) - Todo List (
plans/<name>/todo.md) - Trackable items with status
This skill intentionally does not author per-phase implementation plans (plans/<name>/implementation/phase-N-impl.md).
Default next step (second pass): use author-and-verify-implementation-plan to author/verify the per-phase implementation plan against current repo reality.
When to Use
- When work is multi-phase or too large for a single session.
- When the user explicitly requests a persistent plan.
- When durable coordination or tracking is needed across agents, contributors, or sessions.
Do NOT use for a single bounded work package that can be gated with an inline brief containing its task, DoD, constraints, and final verification. Significance or non-triviality alone does not require plans/ persistence.
Execution Model (Recommended)
- Preferred: the primary agent runs this skill and writes artifacts under
plans/<name>/. - Rationale: plans are conversation-anchored (requirements, trade-offs, sequencing, DoD). Moving authorship to a subagent risks losing intent and introducing gaps.
- Read existing documentation first. Use
doc-exploreronly when bounded codebase impact/symbol analysis is necessary; do not create documentation merely to complete a plan template. - Optional (edge cases): use
doc-exploreronly to materialize/format a large set of plan files after the primary has finalized content and structure.
Routing Matrix (Who does what)
- Writes:
plans/<name>/plan.md,plans/<name>/phases/**,plans/<name>/todo.md, and creates directories underplans/<name>/. - Does NOT write:
plans/<name>/implementation/**(useauthor-and-verify-implementation-plan). - Primary: owns requirements, scope, DoD, phase breakdown, gating.
- doc-explorer: optional for repo-anchored analysis persisted into
docs/**and/or mechanical plan materialization. - implementer: never used for plan authoring.
Workflow
Step 1: Understand the Objective
Gather requirements from the user using the question tool:
- What is the goal? (feature, bugfix, refactoring, migration)
- What problem or current state motivates the change, and what target outcome should replace it?
- Which user-approved decisions and constraints bind the solution?
- What are the functional requirements?
- Which non-functional requirements are explicit, or required by a concrete existing invariant or demonstrated risk?
- What is explicitly out of scope?
- What defines "done"? (Definition of Done)
- What testing strategy is expected?
- Are there assumptions that materially bound scope or acceptance?
If the user provided a detailed brief, extract these from the brief and confirm with the question tool.
Scope and Specification Boundary
Plan the smallest complete solution: the confirmed outcome must work, affected real paths must integrate, and applicable existing invariants must be preserved. Do not invent product rules, guardrails, configurability, abstractions, or future-proofing. Ask the user only for a genuine user-owned fork that changes observable behavior, scope/DoD, policy, or acceptance; resolve codebase-answerable questions through documentation and targeted analysis. Runtime values that operators may change belong in the project's existing configuration pattern.
The full boundary (gold-plating definition, configurable-value rule, and blocking-decision handling) is owned by the execute-work-package skill; this summary is not a separate policy.
Step 2: Analyze the Codebase (if applicable)
If the plan involves changes to existing code:
- Read existing project documentation (
docs/overview.md, module docs) if available - Use the Task tool with
doc-exploreronly for decision-relevant gaps that the existing docs and targeted reads cannot resolve - Identify only dependencies and risks that can change scope, sequencing, acceptance, or feasibility
- Carry decision-relevant context into the plan, but reference detailed architecture documentation instead of reproducing it.
Step 3: Design the Phase Structure
Design the smallest complete plan: use the fewest phases needed for the confirmed outcome and stable execution boundaries while covering all necessary real paths and existing invariants. Omit phases that are useful only for hypothetical future requirements or can be merged without losing a required outcome.
Single-phase plans (work that otherwise warrants persistence):
- One phase covering the entire scope
- Create only the plan, phase, and todo artifacts currently needed
- Use this structure only because the work needs persistent coordination or tracking, or the user requested it; a single-phase shape alone is not a reason to create a plan.
Multi-phase plans (complex features):
- Each phase must be completable in a single session
- Phases should have clear boundaries - no phase should depend on "half-done" work from another phase
- Each phase should produce a testable, committable result
- Order phases by actual dependency while preferring the smallest end-to-end outcome. A separate foundation phase is valid only when its result is immediately required and cannot be delivered directly in the consuming phase.
Guidelines for
阅读完整来源 ↗