wishlist
Add ideas to the roadmap's wishlist in docs/roadmap.md, in its open wishlist PR. Use when the user hands over feature ideas to remember, or to grill later.
- License 许可
- AGPL-3.0
- 所属仓库
- xKirtle/bandmate
- 最近更新
- 2026-11-03
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- wishlist
- description
- Add ideas to the roadmap's wishlist in docs/roadmap.md, in its open wishlist PR. Use when the user hands over feature ideas to remember, or to grill later.
03 SKILL.md 正文
If a gh command fails with HTTP 403: GitHub GraphQL is not available, use its gh api (REST) equivalent from docs/agents/issue-tracker.md instead.
The user is jotting ideas down, not specifying them: record each one as they said it, and leave grilling it for its spec session.
Ideas collect in one open wishlist PR, labelled documentation and no-release-notes and titled "Add … to the wishlist". Only the user merges or closes it; until then, every new idea joins it.
-
Find the wishlist PR:
gh pr list --state open --label no-release-notes --json number,title,headRefNameand take the one whose title ends "to the wishlist". With one, check out its branch and pull. With none, branch from an up-to-datemainasdocs/wishlist-<short-slug>. -
Read
GLOSSARY.mdanddocs/roadmap.md. For each idea, append a## <Name>section todocs/roadmap.md, matching the existing entries:- The heading names the feature as a noun phrase ("Merging Clips", "Playback speed").
- Bullets say what it does, then why, using the user's own real-world case when they gave one ("after a bad Take, record again from the same place").
- Write in the glossary's terms, and steer clear of each term's Avoid words: the user's "mix" may be a Mixdown, or something new that needs a name of its own. Where an idea sits near an existing term or wishlist entry, say how it differs, or extend that entry instead of adding one.
- What the user decided goes in as settled. Every question they left open goes in a closing "Whether …, and …, are for the spec." Settle nothing they didn't.
If an idea is too unclear to name or to tell from an existing feature, ask before writing it.
Done when every idea the user gave has its section, each open question you spotted is named in one, and the page still reads in the same voice.
-
Commit as "Add <ideas> to the wishlist", and push. Open the wishlist PR if there was none, with no issue: a wishlist entry changes no behaviour, so it skips the issue every other change gets. Either way, its title names every idea it now adds ("Add <ideas> to the wishlist"), and its body lists each in one bullet: its name in bold, what it does, and what's left to the spec.
-
Hand back the PR's link, each new idea in a line, and any naming choice you made for them, so the user can veto it.
04 同仓库更多 Skills
parallel-orchestrate
Experimental. Work through an Epic's tickets from /parallel-to-tickets, running tickets that don't contend in parallel sub-agents, and merging each PR once its checks pass and a duplication check clears it.
orchestrate
Work through a queue of GitHub issues one at a time, delegating each to a sub-agent that runs /implement and opens a PR, then waiting for the user's review or, in auto-merge mode, for CI to pass.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
wait-what
Stop. That last message did not land: re-pitch it.