Skip to content

JPeetz/agent-skills / skills/development/finding-unknowns/skills/implementation-plan

implementation-plan

Unverified

Use when planning is requested before a build.

Implementation plan

A plan's job is not to prove you thought of everything. It's to put the reversible-but-expensive decisions in front of the user while changing them is still free. Order the plan by likelihood-of-tweaking, not by build order.

Steps

  1. Open with a three-line summary: what is being built, the approach chosen, and the single riskiest assumption.
  2. Section 1 — Decisions you'll probably want to tweak. Data model changes, new type interfaces, API shapes, anything user-facing. For each: the choice made, one alternative considered, and what changing it later would cost.
  3. Section 2 — Known unknowns and how the plan absorbs them. Where ambiguity remains, state the default that will be taken and the signal that would trigger a pivot. A plan that admits its unknowns survives contact with the territory; one that doesn't just breaks quietly.
  4. Section 3 — The mechanical work. Refactors, wiring, migrations, tests. Compress this; the user trusts you here and reviewing it is a waste of their attention.
  5. End with the review request: the 2-4 specific items you want a yes/no or a pick on before starting.
  6. If the plan is more than a screenful or the user prefers visual artifacts, offer it as a single self-contained HTML page — sections collapsible, tweakable decisions pinned to the top.

Guardrails

  • If a genuinely better approach appears mid-planning, present the pivot as its own decision — don't silently re-plan.
  • Keep it reviewable in minutes. A plan too long to read gets skimmed, and skimmed plans hide bad decisions.
  • The plan should leave room for improvisation during implementation; over-specified plans fail exactly where the territory disagrees with the map.
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 107kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 107kUpdated Claude CodeCodexVerifiedInstall