claude-dev-env 1.40.0 → 1.42.0

package/skills/refine/templates/plan-template.md

@@ -0,0 +1,60 @@
+---
+type: plan
+project: <project-or-topic-area>
+date: <YYYY-MM-DD>
+status: Draft
+tags: [refine, plan]
+---
+
+# <Plan title>
+
+One-paragraph framing of what the plan delivers and why now.
+
+## Goal
+
+What completing this plan produces. Stated as an outcome, not an activity.
+
+## Non-goals
+
+What is intentionally out of scope. Each item is a thing a reader might assume is included.
+
+- <Non-goal one>
+- <Non-goal two>
+
+## Current state
+
+What exists today that this plan builds on or changes. Cite files, hooks, skills, decisions found during the fan-out. Each bullet is one concrete claim with a path or reference.
+
+- `<path/to/file>` — <what it currently does that matters>
+- `<vault note path>` — <decision or prior session this plan inherits from>
+
+## Implementation
+
+Ordered steps. Each step states the file or surface it touches and the concrete change. Subagents to spawn are named with their `subagent_type`.
+
+1. **<Step title>** — <file path or surface>. <Concrete change>.
+2. **<Step title>** — <file path or surface>. <Concrete change>.
+3. **<Step title>** — <file path or surface>. <Concrete change>.
+
+## Decisions log
+
+Each meaningful choice the interview surfaced, with the reasoning. Future-you reads this to understand why the plan looks the way it does.
+
+| Decision | Choice | Reasoning |
+|---|---|---|
+| <Question the interview answered> | <What was chosen> | <Why this over the alternatives> |
+| <Question the interview answered> | <What was chosen> | <Why this over the alternatives> |
+
+## Risks / open questions
+
+What could break this plan, and what is still unresolved. Each item is actionable — either has a mitigation or is flagged for the user to resolve before implementation begins.
+
+- **<Risk one>** — <Mitigation, or "open: needs decision before step N">
+- **<Risk two>** — <Mitigation, or "open: needs decision before step N">
+
+## Acceptance
+
+What "done" looks like. Observable behavior, file existence, command output — concrete and verifiable.
+
+- [ ] <Verifiable outcome one>
+- [ ] <Verifiable outcome two>