Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ user-invocable: true
metadata:
pattern: tool-wrapper
updated: "2026-10-19"
content_hash: "bb1ee37a5ff78641994eb70b3c785307086998dd40a97623a9700e47d24837ca"
content_hash: "be9d0c5997d69513c763f52251e48bb6c7fce9ff24d14a706d639ba1a3c6c3bc"
---

# Plan Manager
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -232,7 +232,8 @@ rewrite never drops the row. Once work has started, `edit` also refuses while
the current record holds such a row. A duplicate or unknown `##` heading blocks every body write; a retired `## Review` heading is dropped on the next write. An explicit `--mode` on `new` outranks any Mode line inside `--goal`; otherwise the last unfenced, unindented Mode line in Goal is the decision.

Advice prints `advice: <text>` on stdout and exits 0. It covers absolute machine
paths, a Research section that holds only `_Not researched yet._` after drafting,
paths, a Research section that is empty or holds only `_Not researched yet._`
after drafting,
defaulted Mode, unknown Effect or Status, an unfinished dependency when a step
moves to in-flight or done, two steps that share a Files path with no Depends
chain, an `edit` that changes Goal, Research, Steps, Acceptance, or Do not touch
Expand Down
9 changes: 7 additions & 2 deletions plugins/plan-lifecycle/skills/productivity/yolo/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ disable-model-invocation: true
metadata:
pattern: pipeline
updated: "2026-10-19"
content_hash: "c88bf4293b208fa56f085e1be92738f8e87a55e4e23c64f2c401b11cef0e5942"
content_hash: "df849a65ed166954017addd24fe9ed277fc24db6e99e4cf601a98f24ebe450b8"
---

# Yolo
Expand Down Expand Up @@ -201,6 +201,11 @@ can write the spec tests.
4. Keep the staged spec tests unchanged while you write production code:
`git diff -- <spec files>` prints nothing. When a spec test is wrong, record
the reason in Verification Results, fix the test, and run the baseline again.
This record replaces the user escalation that `tdd-workflow` asks for.
5. A review fix that changes a spec assertion follows item 4. Run the changed
test against the code before the fix. It must fail on the changed assertion.
Add this line to Verification Results:
`Red baseline, step <id>, review round <r>: <command>: <k> failed, <m> passed`.

## Commits

Expand All @@ -209,7 +214,7 @@ can write the spec tests.
check, and the lint for its files.
2. When you split finished work into commits, check each commit in a temporary
worktree: `git worktree add --detach <path> <sha>`, run the checks, then
`git worktree remove -- <path>`. `<path>` is
`git worktree remove -- <path>` and `git worktree prune`. `<path>` is
`${XDG_DATA_HOME:-$HOME/.local/share}/agent-worktrees/<repository-name>/check-<short-sha>`.
Do not put it under `/tmp` or inside `.git`.
3. Before code review round 1, leave no staged, unstaged, or untracked change of
Expand Down
Loading