agentsclimarketplace

Plan

Skill JHostalek/dotclaude/skills/plan

Use when a task needs an implementation-ready design document before code changes begin.From its SKILL.md

Install
npx -y skills add JHostalek/dotclaude --skill plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.5 KB, as published. Nobody here has run it

task = $ARGUMENTS

Create the minimum implementation-ready plan: one canonical, self-contained HTML artifact with two reading layers. The visual architecture layer is the human approval surface; the execution layer is the complete implementation plan for fresh coding agents with access to the artifact and repository.

Research until the relevant behavior, change surface, constraints, reusable patterns, decisive tradeoffs, and acceptance boundary are clear. Cite repository precedent as file:line wherever the design adopts or departs from an existing pattern. Search current vendor documentation, libraries, and open-source prior art when an unfamiliar API, new pattern, or consequential design choice could change the decision; record the decisive fact and provenance, not the research process. Resolve every material in-scope uncertainty with evidence or user input. Treat hypothetical future needs as non-goals.

<artifact_contract> Save or update docs/plans/<type>-<short-name>.html. Do not create companion requirements, research, task, or handoff files.

Describe the reviewed target state: what must exist and why, one abstraction level above pseudocode. Exclude code, pseudocode, statement-level mechanics, placeholders, open questions, and deferred decisions. Include implementation order, task decomposition, dependencies, and witnessed or repository-derived verification commands in the execution layer.

The artifact must carry all decision context required for implementation. External links are provenance, never required context. Use semantic HTML, in-file CSS, inline SVG where useful, explicit page and text colors, and no external assets or runtime. </artifact_contract>

Visual-first review surface

The first screen is a visual nutshell: outcome, before → after, selected design, scope and non-goals, and observable acceptance. Every non-trivial plan includes at least one decision-bearing visual.

Select views by the question they answer; combine, omit, or introduce another view as the design warrants:

  • before/after for changed behavior;
  • component or boundary map for ownership and structure;
  • sequence or flow view for interactions;
  • state model for lifecycle behavior;
  • wireframe for user-visible states;
  • matrix for meaningful alternatives.

Visuals replace equivalent prose rather than repeat it. Keep labels, legends, and captions precise enough that each visual communicates an implementation constraint, not decoration.

Executor contract

After the visual approval layer, include the concrete implementation plan. It must let one agent execute sequentially or several agents divide work without rediscovering architecture or silently choosing incompatible contracts.

Progressively disclose only what implementation requires:

  • goals, boundaries, observable behavior, and acceptance criteria;
  • the intentional change map: relevant files, symbols, responsibilities, and why each changes;
  • behavioral, interface, data, runtime, and user-state contracts;
  • the selected design, seriously considered alternatives, and decisive evidence;
  • material consequences and mitigations;
  • ordered implementation phases and the dependency between them;
  • within each phase, coherent work packages with owned files/symbols, required behavior, prerequisites, and completion evidence;
  • safe parallelization boundaries and explicit shared files or interfaces requiring coordination;
  • exact repository-derived verification commands at the narrow, phase, and final-gate levels;
  • acceptance criteria mapped to tests, checks, or observable evidence;
  • repository and external references.

Adapt, combine, or omit sections according to the task. Do not create ceremonial coverage. Keep the concise approval surface and detailed executor contract in the same file without duplicating them.

Before saving, read the artifact twice: first as the human deciding whether the architecture is right, then as a fresh coding agent deciding what to change next. If either reader could choose the wrong behavior, interface, boundary, code location, sequence, ownership, or verification, add the missing contract or evidence. Remove statement-level mechanics; retain execution order and coordination constraints.

Present the completed artifact for explicit human approval and stop. Do not implement or run an independent review unless the user requests it. Approval freezes the artifact; a material execution conflict requires revising the affected design and obtaining approval again.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most plan spec skills give

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 73 of 1360
  • Write the spec using the templatein 22 of 1360
  • Ask clarifying questions if neededin 19 of 1360, across 18 files
  • Wait for user confirmation before proceedingin 19 of 1360
  • Save plans to the plans directoryin 17 of 1360, across 13 files
  • Check for product marketing context firstin 16 of 1360, across 5 files
  • Read the plan file completelyin 16 of 1360
  • Order tasks by dependencyin 16 of 1360
  • Gather context from the conversationin 15 of 1360, across 9 files
  • Explore the codebase instead of askingin 15 of 1360, across 13 files
  • Wait for explicit user approvalin 14 of 1360, across 13 files
  • Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

  • Research behavior and constraints thoroughly
  • Cite repository precedent as file and line
  • Resolve every material uncertainty
  • Save the plan as an HTML artifact
  • Include a visual review surface
  • Include an execution layer in the plan

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 612,213. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.