Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

author-and-verify-implementation-plan

Author and verify per-phase implementation plans by cross-checking the gated phase intent against the current source code and existing docs inventories.

DasDigitaleMomentum · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add DasDigitaleMomentum/opencode-processing-skills --skill author-and-verify-implementation-plan

About this skill


name: author-and-verify-implementation-plan description: Author and verify per-phase implementation plans by cross-checking the gated phase intent against the current source code and existing docs inventories. license: MIT compatibility: opencode: ">=0.1" metadata: category: planning phase: implementation

Skill: Author and Verify Implementation Plan

This skill standardizes the second pass between planning and execution:

  • It authors or refines plans/<plan>/implementation/phase-N-impl.md
  • It verifies the plan against the current source code (and uses docs/** inventories when present)

This skill exists to prevent “hand-wavy” implementation plans and reduce drift between phase intent and repo reality.


When to Use

Use this skill when:

  • The phase is already gated (scope/DoD decided in plan.md + phases/phase-N.md).
  • You want the “how” (implementation/phase-N-impl.md) to be grounded in current code.
  • You plan to delegate execution later via execute-work-package.

Do not use this skill to:

  • Change the gated phase intent/scope (that is primary work via update-plan).
  • Generate documentation (use generate-docs / update-docs).

Execution Model

Roles

  • Primary (maintainer)

    • Owns phase gating and decisions.
    • Delegates authoring/verification of the implementation plan when helpful.
    • Reviews the resulting implementation plan for scope compliance.
  • Subagent (delegate or justified model alias)

    • Uses one fresh Delegate session for exactly one phase implementation plan.
    • Reads: phase + existing implementation plan (if any) + relevant docs + relevant code.
    • Writes: plans/**/implementation/phase-N-impl.md.

Routing Matrix (Who does what)

  • Writes: plans/<plan>/implementation/phase-N-impl.md (authoring/refinement grounded against current code).
  • Does NOT write: plans/<plan>/plan.md or plans/<plan>/phases/** (phase intent/scope/DoD remain gated by the primary).
  • Primary: owns phase gating; reviews impl-plan for scope compliance.
  • delegate: performs the author+verify pass and writes the impl-plan. Use delegate-strong only when phase complexity or risk justifies it.
  • implementer: not used for plan artifacts in this skill.

Why plans/ and docs/ matter

  • plans/ is the gated source of truth for intent/scope/DoD.
  • docs/ (if present) provides curated inventories (modules/features/symbols) to navigate quickly.

Scope and Specification Boundary

Author the smallest complete implementation plan: the phase 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. Record a genuine user-owned fork as a blocking Reality Check for the Maintainer; resolve codebase-answerable questions yourself. 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.


Workflow

0) Inputs (Primary → delegate)

Provide:

  • Plan references:
    • plans/<plan>/plan.md (recommended: provides global constraints, scope language, and phase table)
    • plans/<plan>/phases/phase-N.md (required: gated intent/DoD for the target phase)
    • plans/<plan>/implementation/phase-N-impl.md (if exists)
    • plans/<plan>/implementation/phase-(N-1)-impl.md (optional: when the phase builds on previous technical decisions)
  • Only relevant existing docs references, if they materially reduce code discovery
  • Any constraints that must be preserved (naming conventions, verify command preference, etc.).

1) Author + verify

Primary starts a fresh canonical delegate session for the target phase using the bundled prompt template. A justified model alias may be selected without changing the workflow. This is a skill-defined artifact with an explicit output path and canonical template, so it does not require an informal Blueprint.

The delegate:

  1. Reads the plan (for global context) and the phase intent/DoD.
  2. Locates the relevant code areas using docs inventories and targeted code search.
  3. Designs the smallest complete technical change, reusing current structures unless a new element is presently necessary.
  4. Performs one deletion pass: removes or merges any step, new artifact, abstraction, or infrastructure that can be omitted without violating gated scope or a concrete existing invariant. This is author-owned QA, not a review loop.
  5. Writes/updates the implementation plan using the template and ensures it is concrete:
    • references real file paths/symbols
    • traces every implementation step to an authorizing requirement, scope item, acceptance criterion, or existing invariant that must be preserved
    • explains present necessity in the step's Why, rather than adding future-oriented work
    • justifies new modules, layers, interfaces, shared utilities, migrations, or infrastructure with evidence that a direct change to existing structures is insufficient
    • includes a single proposed verify command (or preserves the given one)
    • captures only material mismatches as “Reality Check” notes
    • marks any necessary but ungated user-owned decision as blocking and does not plan work that depends on it

If the phase depends on previous phases, its fresh delegate reads the necessary completed implementation plans to keep continuity. The Maintainer retains phase ordering and cross-phase decisions.

2) Primary review

Primary confirms:

  • The implementation plan stays within the gated phase scope.
  • No evident step or new structure is unnecessary for the phase.
  • The verify command is appropriate.
  • The “Reality Check” section (if any) is acceptable.

Output Contract

The gener

Read the complete source ↗