メニュー
Generate or refine a spec, a feature's immutable contract, from a request, a PRD, or review findings. Use to draft or refine a spec. Do NOT use to write code, a full PRD, or change a locked spec.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | 04-spec |
| description | Generate or refine a spec, a feature's immutable contract, from a request, a PRD, or review findings. Use to draft or refine a spec. Do NOT use to write code, a full PRD, or change a locked spec. |
| argument-hint | build | refine |
Generate or refine the immutable contract for a feature: its target, hard constraints, non-goals, and done-when.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | build | Draft a fresh spec from a request or an existing PRD | a request or a PRD path |
| 02 | refine | Rewrite an existing spec to address review findings | a spec path and the findings |
Dispatch by input: a spec path with findings runs refine; a request or PRD path runs build.
Before running an action, read its file in actions/, not only the table or assets.
TBD: <precise question> rather than guessing. When a request is too vague to draft anything useful, stop and ask for a clearer one.spec.md in the feature folder (aidd_docs/tasks/<yyyy_mm>/<yyyy_mm_dd>_<slug>/), from assets/spec-template.md. Reuse the folder when it exists.assets/spec-template.md: the spec's structure.assets/spec-validator.yml: the checklist a spec is validated against.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.