Repository navigation
docs(guide): one rule for planning a delegated agent's follow-ups - #345
Merged
Merged
Conversation
Quest-Claim: 30da3116cb3d0191
The guide's follow-up rule now says the interview lets the user drop a follow-up and that the caller plans a background agent's follow-ups the same way, so complete.md no longer repeats it. #292 already made merge, complete, and spawn plan follow-ups without offering; this finishes the quest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kixelated
marked this pull request as ready for review
November 1, 2026 06:40
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
kixelated
enabled auto-merge (squash)
November 1, 2026 21:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Finishes Plan delegated follow-ups.
Summary
moq-dev/quest#292 already did most of this quest's Plan:
complete.mdandspawn.mdpoint at the guide;/quest-mergedecides which to plan" now reads "/quest-mergeplans them".#292 also made
/quest-mergerun inline, so the background/quest-mergethat motivated the quest no longer exists.This PR finishes the rest:
assets/AGENTS.md): the follow-up rule now says the/quest-planinterview lets the user drop a follow-up. It also says a background agent's caller plans the reported follow-ups the same way. Before, the guide said only "for its caller to plan".complete.md: drops its own copy of "each interview lets the user drop its follow-up"; the guide now says it.complete.mdandspawn.mdkeep only their timing (after every sub-agent has finished).afk.md: unchanged. It still holds follow-ups for the user, as the Plan says.Choices made without asking
Checks
just checkpasses, includingquest check --base origin/main.just testpasses (734 + 426 tests) when run withCLAUDE_CONFIG_DIRunset. With the variable set, as it is in this session, two tests intest/agent.test.tsfail because the variable leaks into the expected env. That is not caused by this change; quest/m0/agent-test-env.md already tracks it.Review
gpt-6.1-solat medium effort, viaquest review --base origin/mainfrom this Claude Code session.56accd4591d29d78e0b29bc57fb1932051d03c3a, round 1: no findings.Follow-ups
None.
🤖 Generated with Claude Code
(Written by Claude Opus 5.5)