菜单
Phase 4 of design thinking. Execute the plan to produce a working artifact. Input: plan from /ideate and spec from /define. For code: uses superpowers execution skills. For writing/creative: produces the draft artifact. Invoke after Ideate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a repo, project, or area has accumulated several design/spec/plan docs and needs ONE coherent, top-down design document that synthesizes them and routes a reader to the right spec for depth. Create or update after a release or major implementation cycle, when onboarding needs a current architectural view, or when it is unclear which spec is current versus superseded. Trigger phrases: "update the design doc", "sync the design doc", "design-doc", "compile the design", "give me a top-down view of the design".
Phase 2 of design thinking. Synthesize understanding into a precise problem definition and spec. Produces a spec with explicit success/failure criteria. Input: context brief from /understand. Invoke after Understand, or when Ideate reveals the spec is too vague.
Entry point for the 5-phase design thinking process. Assesses current state and routes to the appropriate phase skill. Each phase runs in an isolated agent session and produces a concrete artifact. Phases: understand → define → ideate → prototype → test. Invoke when starting any non-trivial problem or creative task.
Phase 3 of design thinking. Generate and select an approach, then produce a concrete implementation plan. Input: spec from /define. Invoke after Define, or when Prototype reveals a fundamental design issue requiring replanning.
Phase 5 of design thinking. Audit the implementation against the spec. Produces an audit document. Input: implementation from /prototype + spec from /define. Invoke after Prototype. NOT the same as /design-doc — this evaluates a specific implementation cycle, not the system's full architecture.
Phase 1 of design thinking. Map the problem space thoroughly before defining or solving. Produces a context brief. Invoke at the start of any non-trivial problem, or when a later phase reveals the problem was not well understood.
| name | prototype |
| description | Phase 4 of design thinking. Execute the plan to produce a working artifact. Input: plan from /ideate and spec from /define. For code: uses superpowers execution skills. For writing/creative: produces the draft artifact. Invoke after Ideate. |
Using prototype to execute the plan and produce a working artifact.
Implement the plan and produce a working artifact: code committed, document written, or other concrete deliverable.
Read docs/dt/plan.md (primary) and docs/dt/spec.md (success criteria reference) before doing anything else.
Invoke superpowers:subagent-driven-development or superpowers:executing-plans — do not reinvent execution. The plan's task breakdown is the input. The spec's success criteria are the acceptance bar.
Follow the plan's task breakdown. Produce each section or draft in order. Use the spec to verify you are producing what was asked for, not what seems interesting.
Follow plan tasks in order. Produce each deliverable before moving to the next. Do not batch-produce — one task at a time allows early course correction.
Prototype does NOT write to docs/dt/. It writes to wherever the artifact lives:
src/, lib/, wherever the repo puts it.vault/Efforts/Projects/<name>/, or wherever the project lives.The docs/dt/ directory is for design-thinking process artifacts only.
Before declaring Prototype complete, do a quick pass against the spec:
This is a gap check, not a full evaluation — that is Test's job. Do not attempt to evaluate quality or correctness in detail here. If there are obvious omissions, fill them. If the gap is fundamental (wrong approach, spec was wrong), back-transition rather than pushing through.
plan.md with what changed and why).spec.md).Do not back-transition silently. Update the relevant artifact before reopening that phase.
Phase complete: Prototype
Artifact: [describe what was built and where — commit hash for code, file path for docs]
Next: open a new agent session, invoke /test, read docs/dt/spec.md and review the implementation.
Back-transitions: if fundamental design issue discovered → /ideate (or /define if spec was wrong)