본문으로 건너뛰기
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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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-skills3532026년 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-skills3532026년 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-skills3532026년 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-skills3532026년 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-skills3532026년 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-skills3532026년 9월 28일 업데이트

Neeeophytee의 스킬 모두 보기

이 스킬의 문제 신고