Skip to content
Skills Library
Management & product · Planning

implementation-planning

/implementation-planning

Turn an agreed recommendation into a feasible roadmap and implementation plan. Use for sequencing, workstreams, dependencies, resources, rollout gates, recovery plans, and the business case needed to fund execution.

Author
anotb ↗
Licence
MIT
Last repository change
06.09.2026

Assessment and security

85/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content20 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Turn an agreed recommendation into a feasible roadmap and implementation plan. Use for sequencing, workstreams, dependencies, resources, rollout gates, recovery plans, and the business case needed to fund execution.

Original author description

Turn an agreed recommendation into a feasible roadmap and implementation plan. Use for sequencing, workstreams, dependencies, resources, rollout gates, recovery plans, and the business case needed to fund execution.

How it works

  1. Choose the feasible approach
  2. Sequence the work
  3. Assign ownership and control
  4. Deliver and check
Original SKILL.md headings · 33 lines, 533 words
SKILL.md preview
---
name: implementation-planning
description: "Turn an agreed recommendation into a feasible roadmap and implementation plan. Use for sequencing, workstreams, dependencies, resources, rollout gates, recovery plans, and the business case needed to fund execution."
license: MIT
metadata:
  category: engagement-delivery
  version: "2.2.0"
  author: Anot
---

# Implementation Planning

Produce a plan that respects funding, capacity, dependencies, and the decision already made. Enter at the requested stage: compare execution approaches, secure funding, design a roadmap, detail workstreams, or recover a slipping plan. Do not repeat strategy or build a new business case when the direction and funding are already approved.

Use the supplied recommendation, constraints, milestones, resource availability, and baseline. Mark unknowns and proceed with supported portions. Ask only when a missing input prevents a useful or defensible plan. Label estimated durations, proposed owners, and unapproved dates explicitly; do not invent commitments.

## Choose the feasible approach

Where execution choices are open, compare materially different approaches, including defer or continue current operations when relevant. Screen hard constraints before weighted preferences. A high score cannot compensate for missing legal eligibility, unaffordable peak funding, or unavailable capacity. Use weights only when they represent the decision-maker's priorities; test whether plausible changes alter the choice.

If funding analysis is requested, show incremental costs and benefits, timing, downside, and funding need against a consistent baseline. Distinguish released capacity from cash savings, and revenue from contribution. Use financial-modeling if available for substantial calculations; this workflow does not depend on that skill being installed. Do not invent a hurdle rate or add a standard contingency percentage to make a plan look complete.

## Sequence the work

Define outcomes and acceptance criteria before assigning activities. Group workstreams by manageable responsibility and explicit interfaces. Map dependencies, required client decisions, vendor lead times, and business calendar constraints before committing dates.

Use [scheduling and resourcing](references/scheduling-and-resourcing.md) for critical paths, effort, capacity, and recovery. Distinguish target dates from feasible forecasts. Protect business continuity and account for parallel operations, training, adoption, support, and benefit measurement where relevant.

Choose rollout gates that release commitment as evidence improves. State the evidence needed, authority, and responses: proceed, proceed with bounded conditions, revise, or stop. These are gates for executing the plan, not prerequisites for drafting later phases. Provisional later phases can remain useful while earlier evidence is pending.

## Assign ownership and control

Give each deliverable an accountable role and the people doing the work. In a RACI, normally assign one A and at least one R, with combined A/R allowed on small teams. Confirm how joint legal authorities or mandated approvals are represented without hiding them in a simplified matrix. Keep consulted roles limited to those whose input changes the work.

Use the client's existing governance where supplied. Set escalation by materiality, remaining decision time, and authority rather than generic two-week or 10% cutoffs. For ongoing reporting, project-governance can help when available. Separate consulting recommendations from client approval and spending authority.

## Deliver and check

Present the outcome, sequence, workstreams, milestone evidence, dependencies, capacity, budget, risks, and immediate decision or action at the requested depth. A short roadmap does not require a full program handbook.

Verify dates follow dependencies, resource demand fits availability, budgets reconcile, and benefits have a measurement owner. Show the limiting constraint and the consequence of delay. For a recovery plan, distinguish the original baseline, current forecast, and proposed reset; do not erase slippage by silently replacing the baseline. State the trigger and fallback for the risks that could defeat the plan.
Files in this package (2)
  • SKILL.md 4 KB
  • references/scheduling-and-resourcing.md 3 KB

Versions

RepositoryScoreLicence
This page · anotb/management-consulting-plugin85MIT
magnus919/agent-skills100MIT
raoofaltaher/science-ultrapowers100MIT
neuromechanist/research-skills100BSD-3-Clause
w7Pratham/planning-skills100MIT
forgivesam168/ai-dev-workflow100Apache-2.0
cbrock84/headcount90MIT
zeeshanhanif/agentic-sdlc-kit90Apache-2.0
jagreehal/jagreehal-claude-skills90MIT

Database snapshot: 13.11.2026 · package version 1145246022e5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100plan
    Create and manage implementation plans in .agent/plan/ files. Use this skill when: starting a new feature or refactor, the user says "plan this", "think about how to", "design the approach", "prepare a plan", or any time structured planning is needed before execution. Plans are…
  • 100np-business-project-dependencies
    Plan technology project dependencies. Use when a project team needs a feasible sequence and accountable handoffs.
  • 100new
    Create and manage implementation plans in .agent/plan/ files. Use this skill when: starting a new feature or refactor, the user says "plan this", "think about how to", "design the approach", "prepare a plan", or any time structured planning is needed before execution. Plans are…
  • 95Plan
    Generate implementation plans from feature specifications with foundation-aware template selection, dependency analysis, and phased execution strategy. USE WHEN plan, implementation plan, how to implement, execution plan, technical approach, planning, create plan.
  • 81spec
    Synthesises agreed discussion into local change specification. Use when user requests spec, PRD, or implementation handoff.
  • 85implementation-roadmap
    Use when a supply chain director asks something like \"Lay out a twelve-month plan for putting these protections in place\

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.