القائمة
Draft an Architecture Decision Record and store it as a gest artifact (e.g. /write-adr "storage backend choice").
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | write-adr |
| description | Draft an Architecture Decision Record and store it as a gest artifact (e.g. /write-adr "storage backend choice"). |
| args | <decision topic> |
Draft an Architecture Decision Record. ADRs are stored as gest artifacts during drafting and committed to docs/design/
during implementation.
Check existing ADRs in docs/design/ to determine the next sequential ID. During initial drafting, use id: draft and
# ADR-DRAFT: Title.
Use the template from docs/process/writing-adrs.md. Key sections:
Omit any section or frontmatter field that doesn't apply. Do not include empty sections.
Present the draft and iterate. ADRs should be clear enough that a future contributor can understand the decision without additional context.
Pipe the ADR 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 adr --tag "<area>" -q
<adr content here>
EOF
Title is a positional argument in v0.5.0. Categorization is tag-driven: include the adr
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: invoke /implement <id> when you're ready for the next step
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>).