[kixelated]

Plans quest changes from a month-long audit of the moq maintainer's Claude Code transcripts. The audit looked for steering the maintainer typed again and again. Each finding was checked against the skill text on main. Where an existing quest already covered a finding, the finding went into that quest.

Changes

• Re-created: quest/m0/helpers/afk.md. It now plans /quest-afk, a skill of its own that replaces the afk argument kixelated/quest#166 landed on two skills. The skill skips every decision and leaves it on the PR. It keeps starting agents and PRs for work already agreed. The guide gains a rule that every quest skill ends with a final summary in sections. There is no wind-down mode.
• New: quest/m0/helpers/guide-rules.md [S]. It covers:
  • no rebase or force-push on a branch another session may hold;
  • checking that the PR is still open before every push;
  • what a sub-agent's brief carries;
  • marking a complete quest's PR ready, listing choices made without asking;
  • searching for duplicates first in plan;
  • milestone and rank changes being the user's call in audit;
  • follow-ups only as quests;
  • whose review counts;
  • iterate deferring to the repo on maintainer-owned decisions.
• New: quest/m0/helpers/complete-loop.md [S]. /quest-complete re-scans PRs whenever a sub-agent reports or a merge wait wakes. "Accept all" never covers a merge. Holds persist across refreshes and sub-agents. Review rounds are counted from the PR timeline.
• Moved into guide-rules.md (planned for start.md): mark the PR ready when the quest is complete, and list choices made without asking in its body. This drops the skill's "settled every decision, including choices you made without asking" gate.
• Folded into pr-states.md:
  • --land defaults to a merge commit, and the repo's instructions can name another method;
  • the moq.pro label-queue carve-out is dropped;
  • every command refuses a merged or closed PR.
• Reordered quest/m0/helpers/README.md: afk and guide-rules rank first, and complete-loop follows pr-states.

Merging main

Main landed several of these helpers while this PR was open, so merging it changed the plan:

• kixelated/quest#166 landed the afk argument and deleted afk.md. The recorded decision stands, so afk.md is re-created to replace that argument: delete the ## Unattended sections in complete and spawn and the README's afk sentence, and add /quest-afk.
• kixelated/quest#167 landed quest start and deleted start.md. Neither folded item is on main: the guide marks a complete quest ready, but the start skill still has the "settled every decision" gate, and nothing asks to list choices made without asking. Both moved into guide-rules.md, since no other live quest owns the start skill.
• pr-states.md keeps main's text and drops its Required link to the landed quest start. Its merge-method and merged-PR-refusal items stay: the PR state commands don't exist yet, and the merge skill still names no method.
• The helpers README drops the landed status, move, wait-checks, and quest start entries. The rest keeps the recorded ranks: afk and guide-rules first, then pr-states, complete-loop, and headless-agents.
• complete-loop.md and the other guide-rules.md items were re-checked against main's guide and skills after kixelated/quest#157, kixelated/quest#159, kixelated/quest#164, kixelated/quest#167, kixelated/quest#169, and kixelated/quest#172. None had landed. The claim-push exemption now names quest start, which makes that push.

Dropped: filtering CodeRabbit and Codex notices in quest wait. Vendor-specific filters would break the core's independence.

At the user's request, the old one-line skills were removed ahead of /quest-afk:

• kixelated/skills#8
• moq-dev/moq#6200
• kixelated/dotfiles@547de90
• moq-dev/moq.pro@a5dbff3

The moq.pro commit landed on main directly, through push.default=upstream, which is a mistake. That is the hazard the guide's explicit-refspec rule warns about.

Two of the user's answers were interpreted:

• "Default to gh merge" is read as gh pr merge --merge, a merge commit.
• "Sections at least" is read as a summary organized under headings, with no fixed table.

Correct either if that's not what was meant.

Decision paper trail

Round 1: overlap and scope

Goal: agents stop needing repeated steering on the 11 findings, planned as quest changes folded into in-flight quests, with no direct skill edits.

• ✅ Confirm
• Narrow scope

Finding 1, wind-down and away modes:

• Guide-level modes (recommended)
• Arguments on 2 skills
• Separate wrap-up quest
• ✅ Other: "rename it to quest-afk, delete afk/recommended. afk should avoid making any decisions and continue as far as possible, leaving any open decisions in the PR"

Findings 2–11 except 10b:

• ✅ Table as shown: 2 into start.md; 4b and the merged-PR refusal into pr-states.md; a complete-loop quest for 3, 4a and 5; a prose quest for 6, 7, 8, 9, 10a and 11
• 2 into the prose quest
• One quest per finding

Finding 10b, quest wait dropping CodeRabbit and Codex notices:

• ✅ Drop it
• Generic filter
• Plan as stated

Round 2: /quest-afk

What it still does on its own:

• In-flight work plus ready quests (recommended)
• In-flight work only
• Also triage idle PRs
• ✅ Other: "just skip any decisions. We should keep spawning new agents/PRs based on what was already agreed."

Wind-down:

• /quest-afk stop (recommended)
• Separate skill
• Same as afk
• ✅ Other: "don't implement wind down"

Return:

• Final table (recommended)
• Interview on return
• ✅ Other: "all of the quest skills should end with a final summary"

Delete the old skills:

• When quest-afk ships (recommended)
• Now
• ✅ Later answer: "delete those skills now actually"

Round 3: details and placement

Final summary form:

• Table, in the afk quest (recommended)
• Table, in the prose quest
• Free-form summary
• ✅ Other: "I don't think we need to be too specific. Sections at least"

Merge method when the repo names none:

• Only allowed method, else ask (recommended)
• Require instructions
• GitHub default
• ✅ Other: "default to gh merge, allowing repos to override it. moq.pro's weird label thing probably isn't worth it and we should remove it anyway."

Ranks:

• ✅ afk and prose first, complete-loop after pr-states
• Append after afk
• Move to m1

Follow-ups

• Remove moq.pro's merge label queue (moq-dev/moq.pro#2510). This needs /quest-plan in moq.pro.

just check and just test pass.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-21T21:28:51.795002Z	f50ce08	Manual request
🔒 Security Review	✅ Completed 2026-10-21T21:28:09.154002Z	f50ce08	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b7b9ff6460

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1c654831bf

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[kixelated]

@codex review

(Written by Claude Opus 5.5)

[chatgpt-codex-connector]

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: f50ce08b5c

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: f50ce08b5c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[kixelated]

Merge summary for f50ce08:

• Merged main into the branch. afk.md was re-created to replace the afk argument from feat(skills): triage unattended with an afk argument #166 with /quest-afk. The ready-at-hand-back items moved into guide-rules.md, because quest start (feat(cli): claim a quest with a draft PR through quest start #167) landed without them. pr-states.md and the helpers README now match main, keeping the recorded ranks. The PR body's "Merging main" section has the details.
• Codex review on f50ce08 found no major issues, and its security review found none. The three earlier findings were fixed in 1c65483 and 66e481b, and their threads are now resolved.
• CI passes. just check and just test pass locally. A quest built from main ran quest check --base origin/main against this head and passed.
• Decision paper trail: unchanged, in the PR body.

Enabling squash auto-merge, bound to this head.

(Written by Claude Opus 5.5)