Menu
Draft a Request for Comments and store it as a gest artifact (e.g. /write-rfc "plugin system").
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 | write-rfc |
| description | Draft a Request for Comments and store it as a gest artifact (e.g. /write-rfc "plugin system"). |
| args | <proposal topic> |
Draft an RFC and store it as a gest artifact. RFCs gather feedback before committing to an approach -- use them for cross-cutting concerns, public API changes, or proposals that benefit from discussion.
Use the template from docs/process/writing-rfcs.md. Key sections:
Present the draft and iterate. An RFC should be detailed enough for someone unfamiliar with the problem to evaluate the proposal.
Pipe the RFC content via stdin. When --body is omitted and stdin is piped, gest reads the body automatically. Use -q
to get the bare artifact ID:
cat <<'EOF' | cargo run -- artifact create "<title>" \
--tag rfc --tag "<area>" -q
<rfc content here>
EOF
Title is a positional argument in v0.5.0. Categorization is tag-driven: include the rfc
tag plus the relevant area tag(s) from docs/process/labels.md.
The -q flag prints only the artifact ID, ready for downstream use.
Print: share the RFC for feedback, then invoke /plan <id> when ready