SkillVaultskills Browse all 1,000+ skills

Architecture · Version 1.0.0 · Reviewed 2026-08-02

Implementation Plan Writer

Make a defensible decision about implementation phase planning and change dependency mapping with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Builds dependency-ordered implementation plans from approved requirements, architecture, repository evidence, and release constraints. It grounds the decision in approved requirements, current architecture, target design, affected code, tests, deployment topology, and ownership and explicitly prevents a task list ordered by folders rather than dependencies, with integration and migration deferred until the end.

₹299 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Implementation phase planning
  • Change dependency mapping
  • Validation and rollback planning

How Implementation Plan Writer works

You provide

Requirements, constraints, and the current topology

It inspects

Critical path and failure boundaries for implementation phase planning

It decides

A change dependency mapping decision with consequences recorded

You verify

Rollout stages with the signal that gates each one

What it checks first

Implementation Plan Writer builds dependency-ordered implementation plans from approved requirements, architecture, repository evidence, and release constraints. It grounds the decision in approved requirements, current architecture, target design, affected code, tests, deployment topology, and ownership and explicitly prevents a task list ordered by folders rather than dependencies, with integration and migration deferred until the end. Use it when the work involves Implementation phase planning, Change dependency mapping, Validation and rollback planning.

  1. The quality attribute that actually constrains the design: latency, consistency, availability, cost, or compliance.
  2. The critical path and the number of network hops on it.
  3. Where state lives and who owns it, since ownership ambiguity becomes a correctness problem.
  4. The failure behavior of every dependency: fail open, fail closed, or degrade.

Failure modes it recognizes

  • Synchronous coupling making availability the product of all dependency availabilities.
  • A shared database creating hidden coupling between nominally independent services.
  • A component with no clear owner, so its failure has no defined response.
  • Distributed transactions attempted across services without a saga or compensation model.

Answers it will reject

  • Selecting a technology before establishing the constraint it is meant to satisfy.
  • Presenting a diagram as a design without the failure and data-consistency model.
  • Optimizing for a hypothetical future scale at the cost of present operability.

Decision rules it applies

  • Make the consistency requirement explicit per operation, not per system.
  • Prefer designs whose failure modes are understood over designs whose peak performance is higher.
  • Record the decision, the rejected alternatives, and the conditions that would reverse it.

Evidence it asks for

  • Quantify load, growth, and latency budget with arithmetic and stated assumptions.
  • Define the rollout stages and the signal that gates each one.
  • Name the reversal path for the decision.

The method inside

  1. Extract decisions, facts, and unresolved questions needed for implementation phase planning.
  2. Organize change dependency mapping around the reader's next decision or action rather than the source order.
  3. Draft validation and rollback planning with source traceability and no invented behavior.
  4. Run a completeness, consistency, audience, and actionability review before returning the artifact.

Deliverables

  • Implementation phase planning assessment
  • Change dependency mapping decision and action plan
  • Validation and rollback planning verification checklist

Evidence requirements

  • Functional and quality requirements
  • Scale, latency, consistency, cost, and compliance constraints
  • Current topology and alternatives considered

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the implementation plan writer to our current implementation phase planning work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with approved requirements, current architecture, target design, affected code, tests, deployment topology, and ownership. The highest-risk failure is a task list ordered by folders rather than dependencies, with integration and migration deferred until the end. Sequence enabling contracts, reversible implementation, integration, rollout, and cleanup with evidence gates. Verify the result by walking each plan step against the repository and confirming prerequisites, outputs, owners, and rollback are explicit.

Boundaries and compatibility

Ideal for

  • Implementation phase planning: produce a decision or artifact grounded in supplied evidence.
  • Change dependency mapping: produce a decision or artifact grounded in supplied evidence.
  • Validation and rollback planning: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Producing a generic reference architecture without requirements
  • Hiding material trade-offs behind best-practice language

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.