メニュー
Generate a flat slash command across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a one-shot slash command. Not for multi-step skills or other artifacts like rules, agents, hooks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| name | 07-command-generate |
| description | Generate a flat slash command across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a one-shot slash command. Not for multi-step skills or other artifacts like rules, agents, hooks. |
| argument-hint | capture-command | write-command | validate |
Write one canonical slash command from intent and render it per confirmed host tool that supports commands, or once as a plugin source.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | capture-command | Capture the goal, location, and arguments | user request |
| 02 | write-command | Write the command file per supported tool | the goal |
| 03 | validate | Check each command file | the files |
Run the actions in order, 01 → 03, and run each action's ## Test before the next.
Before running an action, read its file in actions/, not only the table or assets.
references/command-authoring.md: the contract (forms, placement, frontmatter, arguments, conventions).references/tool-paths.md: per-tool command path, frontmatter, unsupported tools, the gate.assets/command-template.md: command file scaffold.