02-plan
Use when ranking validated pytest speedups from 01-benchmark into an approved, ordered, commit-by-commit plan.
- License 许可
- MIT
- 所属仓库
- tony/skills
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- 02-plan
- description
- Use when ranking validated pytest speedups from 01-benchmark into an approved, ordered, commit-by-commit plan.
- allowed-tools
- [ "Bash", "Read", "Grep", "Glob", "Write", "AskUserQuestion" ]
- argument-hint
- [--max-commits=N] [--min-score=<0..1>] [--force] [--memory-dir=<path>]
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml300 B
03 SKILL.md 正文
02-plan
Turn measured candidates into a reviewable commit plan. This phase writes only
plan.json and state.json, and only after the user approves.
$ARGUMENTS may pass --max-commits=N to cap the plan, --min-score to raise the
inclusion threshold, --force to recompute, and --memory-dir to override the
memory location.
Arithmetic goes through ../../scripts/measure.py and the staleness check
through ../../scripts/isolate.py (Python 3 standard library). Both paths
resolve from this skill's own directory, not the project's working directory:
resolve this file's directory, join each path, print the absolute paths once,
and write those literal paths in each command below where <measure.py> and
<isolate.py> appear.
Step 1: Load and score
Resolve the memory directory by the lookup order in
../../references/memory-schema.md. If none exists or benchmarks.json is
missing, stop with the halted-run shape in ../../references/output-contract.md
and tell the user to run pytest-optimizer:01-benchmark first.
Read benchmarks.json, baseline.json and state.json. The evidence must
still describe this checkout (a clean scan at this HEAD, and every validated
entry carrying the scan's env_token, a patch_sha256 and this HEAD as its
base_head):
$ python3 <isolate.py> stale \
--memory-dir <memory-dir> \
--phase plan
On exit 1, stop with the halted-run shape and send the user to the phase its
rerun names (pytest-optimizer: followed by it).
Score every validated candidate with ../../references/scoring-rubric.md:
judge safety, effort, confidence and reversibility against the rubric anchors,
then pass them with the entry's measured saving. The script derives impact
itself, zero unless the entry's clears_noise is true, and returns the total
and a dropped reason (exit 1 when a dimension is outside 0 to 1):
$ python3 <measure.py> score \
--delta <median_delta> \
--baseline <baseline median> \
--clears-noise \
--safety <0..1> \
--effort <0..1> \
--confidence <0..1> \
--reversibility <0..1>
Leave out --clears-noise when the entry's clears_noise is not true. A
candidate benchmarked as kind: "hygiene" has no timing: pass --hygiene in
place of --delta and --baseline, which skips the noise gate and scores the
other four dimensions. Plan it as a hygiene item, never drop it for saving no
time.
Drop every candidate whose dropped is set. Capture each dropped item's
prerequisite refactor, if any, as a labeled follow-up, never an auto-applied
commit.
Step 2: Order
Score sets priority; the rubric's ordering constraints override it. One speedup
per commit, never bundled. Honor --max-commits and --min-score.
Step 3: Draft commits
For each planned item, draft a commit from
../../templates/commit-message.tmpl, adapting the type(scope) prefix to the
target project's convention. Write the message per
../../references/prose-rules.md. No Co-Authored-By, no "Generated with" or
other tool trailer, no emoji: hosts add them by default. The approval reply shows
the draft subject only; the body goes into plan.json on approval. Keep the draft
in the reply, not on disk: nothing is written until approval.
Confirm each item's files exist at HEAD, unless its patch creates them
(paths are relative to the repository root; exit 1 lists the absent ones):
$ python3 <isolate.py> exists \
--cwd . \
--patch <memory-dir>/<patch> \
--file <each path in files>
An item whose target is absent is not planned: list it under ## Dropped at the gate with "target file absent at HEAD", and count only the kept items in the
hero line. A deselecting item (removes_tests in benchmarks.json) states
"removes N tests from the default run", and its saving reads as time not spent
on those tests, not as a faster suite.
Assemble the plan from the drafted judgment. Pipe a JSON list of items, each with
order, id, commit (subject, body), verify (the project tests and
quality checks), depends_on and score (the four judged dimensions), to the
script; it takes impact, files, token, patch, hash, cache and removed_ids
from benchmarks.json, computes the total and every cumulative expected_total,
and lists the items the rubric drops. Without --out it writes nothing, so it
also previews the plan in plan mode:
$ python3 <measure.py> plan-build \
--memory-dir <memory-dir> \
--draft -
Each saving was measured alone against the control. Independent changes can
overlap (widening a sleeping fixture and removing its sleep do not add), so
never sum the savings or call them recovered: the plan states each as measured
alone, and 03-execute measures the combined result.
Step 4: Present for approval
Enter plan mode before the first edit. In Claude Code call EnterPlanMode; in Cursor, Codex, or Gemini use /plan or Shift+Tab. Where plan mode is unavailable, present the plan as text.
Present the 02-plan
sections from ../../references/output-contract.md. Let the user reorder, drop
items, or cap the count; revise the draft in the reply after each change and write
nothing, since plan mode blocks writes. Plan mode is the decision point, so omit
the AskUserQuestion panel.
Without plan mode, the reply is the same sections as text and nothing else: the hero line comes first and carries the approval request, with no remark about plan mode before it and no closing note after the last section. Wait for the reply:
✓ 1 commit planned; reply "approve" to record the plan, or name items to drop or reorder
## Ranked plan
- 1. H10 mis-scoped fixture: widen make_config to session scope in tests/conftest.py under the subject "tests(fixtures) Widen make_config to session scope", total score 0.87, saved 2.7s measured alone above the 0.44s band, verified with pytest expecting 40 of 40 passing.
## Dropped at the gate
- H33 fixed sleep in test_report: saves 0.03s, inside the noise band, so impact is 0.
Without an interactive session, write nothing and stop: an unapproved plan is not executable.
Once the user approves, exit plan mode and run the same plan-build command
with --out <memory-dir>/plan.json on the approved draft, then hash it:
$ python3 <measure.py> hash <memory-dir>/plan.json
Record the approval, which clears the later flags:
$ python3 <measure.py> state \
complete <memory-dir>/state.json \
--phase plan \
--set 'plan_hash="<hash>"'
plan.json is the contract pytest-optimizer:03-execute consumes; a request that
explicitly says to approve and apply the plan is approval for this plan only.
04 同仓库更多 Skills
serene-bliss
Use when asked to make a CLI --help, docs page, error message, or tooling UX more serene or calmer for developer experience; returns text, no edits.
review
Weave code review: run independent adversarial reviews in parallel, then synthesize findings
refine
Use when asked to refine a draft, iterate on code until cleaner, or polish a README through repeated critique and improvement.
prompt
Weave prompt: compare independent adversarial implementations, then adopt the single best one
plan
Weave planning: compare independent adversarial plans, then synthesize the best one
fix-review
Fix weave review findings: validate, add test coverage, fix, and commit each as atomic changes