Skip to content

feat(skills): hand each quest result to the user with its decisions #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kixelated merged 1 commit into from
Sep 26, 2026
Merged

feat(skills): hand each quest result to the user with its decisions #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 8 additions & 1 deletion .claude/skills/spawn-quests/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,15 @@ Each agent blocks on its own checks and reports back only when done or blocked.
Limit the concurrency to at most N agents in parallel, where N is half the number of physical CPU cores.
Other sessions share this machine: hold new agents while the load average exceeds the core count.

Each agent switches into its own worktree before editing, opens its PR as a draft, and never marks it ready itself.
Its report lists every open decision with a recommendation.
Report each sub-agent's final status, staying silent on interim notifications, but do not monitor their PRs.
Prompt the user if they want to /plan-quests for any suggested follow-ups.

As each agent reports, explain its result in a few lines, then prompt the user inline without waiting for the rest.
Ask about every open decision (naming, API shape, branch, blockers, manual steps), a few per prompt, each with the PR, a short summary, and your recommendation first.
Offer its follow-ups as a multi-select to /plan-quests.
Resume the owning agent with each answer, and prompt again on anything its next report raises.
Once nothing is open, ask whether to mark the PR ready, then mark it yourself.

Run /plan-quests for any selected quests in the foreground.
Perform any research and monitoring in the background.
Expand Down
7 changes: 4 additions & 3 deletions .claude/skills/start-quest/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ Implement the quest until it is complete, or some blocker is hit, then create a
Keep scratch files (PR body, logs, notes) in the worktree's gitignored `.scratch/`.
Never write to or clean up a directory other agents share, such as a session scratchpad.

When done, summarize any issues encountered, and suggest potential follow-up.
If you're happy with the outcome, switch the draft PR to ready for review.
If you want another set of eyes on it, keep it a draft.
When done, explain the result in a few lines and summarize any issues encountered.
Prompt the user interactively for every open decision (naming, API shape, branch, blockers, manual steps), each with your recommendation, and offer follow-ups as a multi-select to /plan-quests.
Keep the PR a draft until the user confirms every decision, then ask whether to mark it ready.
A background agent that cannot prompt lists its decisions in its report instead and leaves the PR a draft.
Loading