Files
ytplayer/.claude/skills/plan-queue/plan-template.md
2026-07-16 20:51:51 +08:00

60 lines
1.6 KiB
Markdown

---
id: NNN-slug-hash # matches filename (without .md)
title: Short imperative title
created: YYYY-MM-DD
depends_on: [] # e.g. [001-add-user-model-a3f9c2]
est_files: 2 # rough count of files the executor will touch
---
# NNN — Title
## Objective
One paragraph: what "done" looks like, in behavioral terms.
## Context the executor must NOT rediscover
Everything a weak model needs so it never explores:
- Exact file paths with line anchors (`src/foo.ts:120-145`) and what's there.
- Signatures of functions/utilities to REUSE (with their paths).
- Pasted snippets of the current code around each edit site.
- Any project conventions that apply (naming, error handling, test style).
```lang
// paste the relevant current code here
```
## Steps
1. Edit `path/to/file.ext` — concrete, mechanical instruction. For tricky
edits, show the exact before/after or a unified diff.
2. Create `path/to/new-file.ext` with: (full contents or precise spec).
3. ...
## Out of scope / do NOT touch
- Files/behaviors the executor must leave alone.
- Refactors NOT to attempt, even if tempting.
## Verification
Run exactly:
```bash
<build/test/lint commands>
```
Expected: <what passing looks like, specific output to check>.
## Report format (executor: follow exactly)
Output ONLY the following, no other prose:
1. `git diff` (unified) of all changes.
2. Raw output of the Verification commands.
3. `Findings:` — max 10 lines: surprises, deviations from the steps, anything
skipped and why.
Do not commit. Do not push. Do not touch files outside the Steps.