القائمة
Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | chaining-spells |
| description | Use when composing multiple spells into a chain that runs end-to-end (e.g. brainstorm -> plan -> execute -> verify). |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | chained |
| time | varies (chain runtime + setup) |
| version | 1.0.0 |
| source | bundled |
Builds and runs a chain — a workflow spell whose stages each invoke another existing spell. The chain handles handoffs, loop-backs, and stop-on-failure.
general-research-loop)A new chain spell (kind: workflow, complexity: chained) saved to $WIZARD_HOME, plus a runnable execution path.
This is a workflow — and the resulting chain is also a workflow. Don't confuse the two.
List the spells in the order they'll run. Verify each exists (in $WIZARD_HOME or bundled). Reject the chain if any are missing — offer to build them first.
For each adjacent pair (A → B):
If they don't match, the chain isn't yet runnable. Either:
What you bring (Inputs) to accept A's output, ORFor each transition, name what must be true to pass to the next stage. Default: "the constituent spell's Quality bar was met."
When does the chain return to an earlier stage?
Default: "if any stage's Quality bar is not met after the constituent finishes, return to that stage and re-run."
Document any custom loop-backs.
Use templates/spell-template-chained.md. Set composes: to the list of constituent names.
Standard tester runs 1-2 scenarios that exercise the full chain. Each constituent must run; each handoff must succeed.
If any constituent fails, the chain test fails. Refine that constituent first; then re-run the chain test.
Save to $WIZARD_HOME/chains/<chain-name>/SKILL.md.
Return to Stage 1 when:
A chain is good enough when:
Chain: general-research-loop
Constituents:
1. breaking-down-a-problem (output: 1-page problem statement)
2. literature-scan (output: list of 5-10 sources)
3. summarizing-a-document (run per source; output: per-source notes)
4. interview-synthesis (output: combined synthesis)
5. verifying-before-citing (discipline; runs throughout)
Handoffs:
- 1 -> 2: problem statement seeds the search query
- 2 -> 3: each source goes to a separate summarize run
- 3 -> 4: combined notes feed synthesis
- 5 is a discipline that doesn't transition; it's loaded throughout
Loop-backs:
- After 4: if synthesis exposes a question the lit-scan missed,
return to stage 2 with the new query
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 the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
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.