菜单
Coordinate multi-agent development via GitHub Discussions. Use when starting a session (discover tasks), claiming work, posting progress, requesting decisions, or completing tasks. Triggers on: "find work", "claim task", "post status", "ask decision", "coordination", "what should I work on".
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/fairchild/workspaces --skill gh-discuss命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Run the cofounder contributor workflow for this repo's standing personas. Use when you want April Clearwater or Plat Ironwood to sweep open PRs, discussions, and issues, then produce one structured action: proposal, discussion comment, PR review, or issue execution that pushes a branch and opens or updates a PR.
Capture deterministic screenshots of the WorkSpaces macOS app in a known UI state. Use when the user asks to "capture a release screenshot", "screenshot the app", "show the Phase 1 state", or wants evidence for a PR / release notes / design brief. Wraps the fixture-mode env vars (WORKSPACES_UI_FIXTURE, WORKSPACES_UI_FIXTURE_AGENT_STATES, and WORKSPACES_UI_FIXTURE_COMMAND_STATUSES) and the bundled scripts/capture.sh capture pipeline. Triggers on "release screenshot", "screenshot the app", "capture the app", "fixture screenshot", "ui evidence", "/release-screenshot".
Repo-specific conventions for briefing implementation subagents and gating their PRs before ready-for-review. Use when fanning work out across parallel subagents/worktrees. Triggers: "delegate this", "spin up agents", "brief a subagent", "gate this PR".
正在显示 SKILL.md
| name | gh-discuss |
| description | Coordinate multi-agent development via GitHub Discussions. Use when starting a session (discover tasks), claiming work, posting progress, requesting decisions, or completing tasks. Triggers on: "find work", "claim task", "post status", "ask decision", "coordination", "what should I work on". |
Agents coordinate through GitHub Discussions — a durable, web-visible layer that works across worktrees, sessions, and tools.
Orientation — which bus am I on? The live execution bus is GitHub Issues + the label taxonomy (
ready/claimed/review/mergeable), driven bysync-execution-state.pyand the Factory review lane. Claim and work issues there — seedocs/agents/triage-labels.mdandbacklog/AGENTS.md. On Discussions, the actively-used flow is the cron team's[idea]→ owner-👍 → planned-issue pipeline (Peter Planner). The[task]/[claimed:]claim-and-complete grammar below is a secondary path for ad-hoc, cross-worktree coordination — reach for it when work doesn't yet have an issue or spans harnesses; use Issues + labels for the standing execution loop.
.agents/skills/gh-discuss/scripts/gh-discuss.py <command>
| Action | Command |
|---|---|
| See current state | gh-discuss.py dashboard |
| Find available work | gh-discuss.py list --unclaimed |
| Create a task | gh-discuss.py create "Title" --body "Details" |
| Create from backlog | gh-discuss.py create --from-backlog backlog/some-plan.md |
| Claim a task | gh-discuss.py claim <NUMBER> |
| Post progress | gh-discuss.py update <NUMBER> "Status message" |
| Complete a task | gh-discuss.py complete <NUMBER> --pr <PR> |
| Abandon a task | gh-discuss.py abandon <NUMBER> |
| Create in specific category | gh-discuss.py create "[idea] Title" --body "Details" --category General |
| Ask a blocking question | gh-discuss.py create --decision "Question?" --body "Options" |
| Check pending decisions | gh-discuss.py list --decisions |
| Verify app credentials | gh-discuss.py setup |
| Live bot identity test | gh-discuss.py verify |
| Run unit tests | test_gh_discuss.py |
| Run all tests (+ live) | test_gh_discuss.py --live |
Uses existing default GitHub Discussion categories — no custom categories needed.
| Category | Purpose |
|---|---|
| General | Task discussions and idea proposals — agents discover, claim, and complete work; cron agents post [idea] proposals |
| Q&A | Blocking decisions — marking an answer unblocks the agent |
| Announcements | Session summaries, protocol changes (human/lead only) |
| Show and tell | Completed work demos |
All discussion titles use machine-parseable prefixes. These are the source of truth for task state — the script filters on them.
[task] Implement workspace creation progress UI
[task][claimed:el-paso-v1] Implement workspace creation progress UI
[decision] Pane tree: reducer vs direct state?
[idea] Quick switcher (Cmd+P) for repo/workspace navigation
[idea][endorsed] Quick switcher — approved by human for implementation
[shipped] Ghostty split actions working
Auto-detected from worktree directory name (e.g. el-paso-v1, albany-v2). Every comment includes a header:
**Agent**: `el-paso-v1` | **Branch**: `feat/progress-ui`
dashboard to see open tasks, claimed work, and pending decisionslist --unclaimed to find available workclaim a task before starting workupdate comments at major milestonescreate --decision to ask for inputlist --decisions for answers to previous questionscomplete finished tasks (link the PR)abandon any tasks you can't finish (frees them for other agents)After claiming, the script re-reads the discussion title to verify the claim stuck. If another agent overwrote it, the claim exits with an error.
Discussions augment backlog/*.md files — they don't replace them.
Create a task from a backlog file:
gh-discuss.py create --from-backlog backlog/some-plan.md
This extracts the first # heading as the title and includes the file content in the discussion body.
Posts as a bot account instead of your personal account. See references/github-app-setup.md for setup instructions. Run gh-discuss.py setup to validate credentials.