NagareNegishi/DJ-App / .claude/skills/plan-impl
plan-impl
VerifiedUse this skill whenever the user wants a rough implementation plan — the "how", e.g. breaking a feature into build steps — from an existing product plan, or hands off from `plan-product`. Drafts a doc only; deep verification is the separate `plan-verify` skill.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.1 KB |
SKILL.md
View on GitHub---
name: plan-impl
description: Use this skill whenever the user wants a rough implementation plan — the "how", e.g. breaking a feature into build steps — from an existing product plan, or hands off from `plan-product`. Drafts a doc only; deep verification is the separate `plan-verify` skill.
---
# Plan Impl
Turn a mature product doc into a rough implementation plan — structure and
high-level steps. Middle skill in the chain: `plan-product` → **`plan-impl`** →
`plan-verify`.
## Input, output, and the handoff gate
- Read `docs/plans/<slug>/product.md`. If it is missing, stop and tell the user
to run `plan-product` first.
- **Gate:** every entry in `product.md` must be at `🤖 ai-audited(...)` or above.
Read this from the `## Maturity` header — if `lowest:` is `🌱 idea`, stop and
tell the user to run an audit pass in `plan-product`. Do not rescan every entry
to decide, and do not audit `product.md` yourself here.
- Write to `docs/plans/<slug>/impl.md` — always this path. Regenerating it
overwrites freely. Docs only: never change code, run git, or make a network
call.
## Two marks per step, kept separate
Every step carries a maturity mark **and** a verification mark, stacked on one
line: `🤖 ai-audited(opus-4.8) · ❔ unverified (net-new)`.
Maturity — same axis and same rules as `plan-product`:
```
🌱 idea 🤖 ai-audited(<model>) 👤 human-ok ✅ settled
```
Advance a step to `🤖 ai-audited(<model>)` on your own. Stamp `👤 human-ok` or
`✅ settled` only when the user explicitly instructs you to set that mark on a
named step: ask, wait for the instruction, then stamp — one step per instruction.
Never stamp either mark on your own initiative, and never reuse one step's
instruction for another.
Verification — this skill leaves almost everything unverified:
```
❔ unverified (not checked) step names existing code/tools but nothing was opened
❔ unverified (net-new) step builds new code, so there is legitimately nothing to link yet
```
Do **not** mark any step `🔗 verified` here — attaching real proof is
`plan-verify`'s job. Use `(net-new)` only for genuinely new code; when a step
leans on something that should already exist but you have not opened it, use
`(not checked)` so `plan-verify` knows to look.
## File format — follow this exactly
```markdown
# Implementation plan: <slug>
## Maturity
lowest: 🌱 idea
🌱 idea 4 · 🤖 ai-audited 2 · 👤 human-ok 0 · ✅ settled 0
## Overview
🤖 ai-audited(opus-4.8) · ❔ unverified (not checked)
<2–4 sentences: the shape of the build and the main moving parts.>
## Risks & unknowns
🌱 idea · ❔ unverified (not checked)
- <feasibility risk, dependency, or thing that could force a redesign.>
## Steps
### Step 1: <short imperative title>
🌱 idea · ❔ unverified (net-new)
<what to build and roughly where. Name files/modules when known — they get
verified later, not now.>
### Step 2: <...>
🤖 ai-audited(opus-4.8) · ❔ unverified (not checked)
<...>
```
## Rules
- **Stay rough.** High-level steps that expose unknowns and feasibility risks,
not line-by-line instructions or code on paper.
- **`Risks & unknowns` is required** — never omit it. If a step depends on
something you are unsure exists or works, say so there and mark the step
`(not checked)`.
- Each step is a coherent unit of work with a clear boundary — not a micro-task,
not a mega-task.
- **Header can't drift.** Update the `## Maturity` header in the same pass as any
entry. Counts cover every marked entry (Overview, Risks, and each step).
- Never assert a file, function, or library API exists as fact. Phrase such
steps as intent, and leave them unverified.
## human-writing
Follow the `human-writing` skill for the prose.
## After writing
Do not render the doc in chat. Show the path and offer:
1. **Revise** — reshape steps, rewrite the file, update the header.
2. **Run `plan-verify`** — once the product doc is settled and stable, to harden
this rough plan into a verified one. Remind the user `plan-verify` is
command-only and spends the real verification budget.
3. **Stop** — the doc stays for later.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |