메뉴
Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Use when the user wants to capture a repeatable task as a reusable spell, or asks "how do I build a workflow / skill / framework for X"
Use when the meta-builder routes to kind=subagent. Generates a spell that dispatches one or more subagents to do work in parallel or in isolation.
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
Use when browsing what spells are available - bundled seeds, your personal library, or both. Filter by kind, audience, or update status.
Use when the user invokes /capture-this-chat or /build-spell --from-transcript. Reads a transcript and produces a context dictionary plus a draft SKILL.md, which hands off to building-a-spell at Stage 2.
| name | building-a-workflow-spell |
| description | Use when the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions. |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | guided |
| time | 15-30 min |
| version | 1.0.0 |
| source | bundled |
Specialist builder for kind: workflow spells. A workflow has multiple stages with explicit handoff artifacts and checkpoints between them.
building-a-spell Stage 2 when kind: workflowA draft SKILL.md with explicit Stages, Checkpoints, and Loop-back conditions sections, ready for the standard tester.
This is a workflow chain.
A stage is a place where you could (and sometimes do) stop, hand the work to someone else, and return to it later.
Ask the user (or extract): "What are the natural stopping points in this process?"
If the user says "no stopping points, it's one continuous flow" — this isn't a workflow; it's a content kind. Re-route.
Each stage has:
If you can't name the output artifact, the stage isn't well-defined yet. Sharpen.
For each stage transition, write the checkpoint — what must be true to pass the gate.
Checkpoints are tested, not asserted. Each checkpoint should be verifiable: the artifact has a property you can check.
A workflow without loop-backs is a pipeline (one-way). Most real workflows loop back — when the artifact at stage N reveals stage N-1 was wrong.
Capture loop-back conditions explicitly. If there are none, that's a finding — confirm with user.
When stages are themselves named spells, add a composes field to frontmatter:
composes:
- <constituent-spell-1>
- <constituent-spell-2>
This makes the workflow a chain. See chaining-spells/SKILL.md for details on chain mechanics.
Standard mode (not discipline mode). Tester runs 2-3 scenarios end-to-end through all stages.
If a checkpoint repeatedly fails, that stage's checkpoint is wrong (too strict or too loose). Refine in Stage 3.
Return the PASSing draft.
Return to Stage 2 when:
The draft is good enough when:
composes is set, every name resolvesWorkflow: structured-literature-review
Stages:
1. Define the question (output: 1-sentence research question)
2. Snowball search (output: 20-30 candidate papers)
3. Screen by abstract (output: 8-12 included papers)
4. Extract findings (output: per-paper extraction sheet)
5. Synthesize (output: 1-page synthesis)
Checkpoints:
- After 1: question is single-sentence and falsifiable
- After 2: candidate count >= 20
- After 3: inclusion criteria documented
- After 4: every included paper has a filled extraction sheet
- After 5: synthesis cites every included paper
Loop-backs:
- After 3: if <8 included, return to stage 2 (broaden search)
- After 5: if synthesis exposes a contradiction, return to stage 4 (re-extract)