Menu
Promote a gest spec to a GitHub Discussion (e.g. /promote-spec <id>).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Take an iteration and execute it: dispatch /implement agents per phase, always sequentially (e.g. /orchestrate <iteration-id>).
Take an iteration and execute it: dispatch /implement agents per phase with git worktree isolation for parallel work (e.g. /orchestrate <iteration-id>).
Take an iteration and execute it: dispatch /implement agents per phase with jj workspace isolation for parallel work (e.g. /orchestrate <iteration-id>).
Promote a gest task to a GitHub Issue (e.g. /promote-task <id>).
Explore a rough idea with the user, clarify requirements, and draft a spec. Also decomposes large specs into smaller ones (e.g. /brainstorm "offline mode", /brainstorm <gest-id>).
Implement a single issue: write code, verify, review, format, and commit (e.g. /implement <gest-id>).
| name | promote-spec |
| description | Promote a gest spec to a GitHub Discussion (e.g. /promote-spec <id>). |
| args | <gest-id> |
Promote a gest spec artifact to a GitHub Discussion.
cargo run -- artifact show <id> --json
Extract:
title — becomes the discussion titlebody — becomes the discussion body (see sanitization rules below)Sanitize the body before promoting. The discussion body must not contain internal gest references. Remove or rewrite
any gest short IDs (e.g. ktxolxqz), gest task/artifact <id> references, or sections that only list gest entities as
dependencies. Replace gest IDs with the entity's title where context is needed. Do not repeat the title as an # H1
heading in the body — GitHub already displays the title prominently.
All specs are promoted to the Ideas discussion category.
Draft the discussion creation and present it to the user for confirmation. Use the gh api to create the discussion:
# First, get the repository ID and Ideas category ID
gh api graphql -f query='
query {
repository(owner: "<owner>", name: "<repo>") {
id
discussionCategories(first: 25) {
nodes { id name }
}
}
}
'
Then create the discussion:
gh api graphql -f query='
mutation {
createDiscussion(input: {
repositoryId: "<repo-id>",
categoryId: "<ideas-category-id>",
title: "<title>",
body: "<body>"
}) {
discussion { url }
}
}
'
After the user confirms, execute the commands. Extract the discussion URL from the response, then store it as artifact metadata:
cargo run -- artifact meta set <id> github-discussion <url>
Print a summary: the GitHub Discussion URL.
Print: the spec has been promoted and linked via metadata