本文へ移動
cccskills
無料GitHub で公開

implementation-plan

Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.

日本語の概要は準備中です。原文の説明を表示しています。

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."

日本語の概要は準備中です。原文の説明を表示しています。

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.

日本語の概要は準備中です。原文の説明を表示しています。

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.

日本語の概要は準備中です。原文の説明を表示しています。

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.

日本語の概要は準備中です。原文の説明を表示しています。

Neeeophytee/finding-unknowns-skills3462026年9月28日 更新

Neeeophytee のスキルをすべて見る

このスキルの問題を報告する