القائمة
Draft an issue and store it as a gest task (e.g. /write-issue "add CLI flag parsing").
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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-issue |
| description | Draft an issue and store it as a gest task (e.g. /write-issue "add CLI flag parsing"). |
| args | <issue topic and context> |
Draft an issue and store it as a gest task.
Use this structure. Omit any section that is not relevant — only User Story and Acceptance Criteria are required.
# <Title>
## User Story
As a <role>, I want <goal> so that <benefit>.
## Acceptance Criteria
- <measurable criterion>
- <measurable criterion>
## Dependencies
- `<gest-id>` — <why needed>, or "None"
## File Structure
- `<path>` — <what goes here>
Pipe the issue content via stdin as the description. When -d is omitted and stdin is piped, gest reads the description
automatically. Use -q to get the bare task ID. Apply tags for type, area, and priority using the vocabulary from
docs/process/labels.md. Use bare tags -- no namespace prefixes like area: or type::
cat <<'EOF' | cargo run -- task create "<title>" \
--tag "enhancement,cli,p2" -q
<issue content here>
EOF
Tag examples: bug, enhancement, chore, cli, model, storage, server, ui, config, docs, p0-p4.
Inline flags available at creation time (use when the caller provides context):
--phase <n> -- execution phase for parallel grouping-p <0-4> -- priority level (0 is highest)-l <rel>:<target_id> -- create a link (repeatable, e.g. -l child-of:abcd1234 -l blocked-by:efgh5678)-i <iteration-id> -- add the task to an iterationThe -q flag prints only the task ID, ready for downstream use.
Print: invoke /implement <id> when you're ready for the next step