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
3 changes: 3 additions & 0 deletions assets/AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -241,6 +241,9 @@ Recommend in every prompt, a multiple-choice list included, and give a one-line
An answer such as "whatever you recommend" picks your recommendations; act on them without asking again.
Do not use asynchronous question tools.

A dialog for a decision, plan, or follow-up offers concrete choices and keeps one option for "Explain it first", which walks the user through the problem, current behavior, and each choice's trade-offs, then asks again without it.
A dialog for a step only the user can take offers, in this order: the agent taking it, such as by driving the browser, when it plausibly can; "Done / I'll do it now"; "Not at my PC (defer)", which keeps the wait and skips it for the session; and "Drop the wait", which a tool holding fewer options leaves to the user's typed answer.

If no blocking tool is available, or it returns without an answer, put the question and numbered choices in your final reply and end the turn.
Resume when the user answers; do not bury the question in a progress update or wait with sleeps or timed polls.
Silence, elapsed time, and a preselected recommendation are not answers or approval.
Expand Down
1 change: 0 additions & 1 deletion assets/skills/merge.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,5 @@ A PR that left the queue unmerged shows why under `landing-stopped` in `quest st
Never close a PR to unstick it, and never work around a refused merge; ask instead.

Ask the user for the pick with your recommended action, one of `/quest-merge`, `/quest-iterate`, skip, or delete, plus `/quest-merge` when you recommend another, "Explain it first", and "Rethink it".
"Explain it first" walks them through the change and its open choices; ask again without it.
"Rethink it" starts a fresh background sub-agent, given the PR, its reviews and threads, and its quest's Goal, Plan, and evidence (read the deleted file on the base), not your recommendation, to start from scratch: brainstorm other approaches to the problem, decide whether this PR is the best path forward, and recommend merging it, iterating toward a named alternative, or dropping it.
Ask again without it, its recommendation beside yours, and where they differ.
2 changes: 1 addition & 1 deletion assets/skills/plan.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Search by the code and behavior the work touches, not only its keywords: a quest
Show any overlap in the first round.

Interview the user with the grill skill.
The goal is the root of its tree, so the first round asks only it: restate the observable outcome, why it matters, and its boundaries and non-goals in one sentence, and get that confirmed before any other question.
The goal is the root of its tree, so the first round asks only it: restate the observable outcome, why it matters, and its boundaries and non-goals in one sentence, and get that confirmed before any other question, with "Drop" among its options for work not worth planning.

Choose the structure yourself rather than asking: one quest per independently completable outcome, an epic for related ones, an edit to an existing quest that already owns the work, and the milestone each new quest joins, by its urgency and by any milestone rule the user has stated, such as "CI and flakes join m0".
Show that structure in the summary, with each quest's size and milestone and the reason for the milestone, so the user can correct it in the PR's review.
Expand Down
7 changes: 2 additions & 5 deletions assets/skills/review.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,11 +52,8 @@ Once the reset passes or the login is restored, the item has cleared: whoever fi
Push, resolve each `duplicate` line `quest status <pr>` then prints as the guide's Creation describes, then mark the PR ready for review: with `quest ready <pr> <token>`, which also drops its `## Waiting` section, or with `gh pr ready <pr>` for a draft you reviewed without a hold.

Summarize the review, with its last round's score and rationale, and CI from `quest status <pr>`.
Name any decisions the review raised without answering them, then ask the user for the pick as `/quest-merge` describes, recommending one of:
- `/quest-merge`: the PR is landable as `/quest-merge` defines it, or will be once fixed with no decision left for the user, such as failing checks or unaddressed automated review findings; `/quest-merge` runs `/quest-iterate` on it first.
- `/quest-iterate`: the review raised significant issues or decisions, which it settles with the grill skill's interview.
- skip: the PR should not be merged yet.
- delete: the quest should be deleted.
Name any decisions the review raised without answering them, then ask the user for the pick with `/quest-merge`'s options.
Recommend `/quest-merge` when the PR is landable as it defines, or will be once fixed with no decision left for the user, such as failing checks or unaddressed automated review findings, since `/quest-merge` runs `/quest-iterate` first; recommend `/quest-iterate` when the review raised significant issues or decisions.

While its required checks are still running, report that instead of asking; `/quest-run` asks once they finish.

Expand Down
36 changes: 0 additions & 36 deletions quest/m0/dialog-options.md

This file was deleted.