菜单
Use during try-it for kind=discipline spells. Orchestrates baseline + with-skill comparison via the discipline-mode tester to prove the rule actually changes behavior under rationalization pressure.
用 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 the meta-builder routes to kind=workflow. Generates a workflow spell with explicit stages, checkpoints, and loop-back conditions.
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.
| name | pressure-testing-a-spell |
| description | Use during try-it for kind=discipline spells. Orchestrates baseline + with-skill comparison via the discipline-mode tester to prove the rule actually changes behavior under rationalization pressure. |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | guided |
| time | 5-15 min |
| version | 1.0.0 |
| source | bundled |
Tests a discipline-kind spell against rationalization. The test runs each scenario twice: once without the skill loaded (baseline) and once with it loaded (with-skill). The skill is only PASS if the with-skill run holds the rule that the baseline run violated.
This is what makes a discipline skill different from a description: proof it changes behavior.
building-a-discipline-spell Stage 5refining-a-spell when a discipline skill changedA PASS / NEEDS-REFINEMENT verdict, plus the specific rationalizations that slipped through if any.
This is a workflow.
Read the draft's Excuses and counters table. Each row implies a pressure scenario:
If the excuse is "It's a small fact, I don't need to verify"... ...then the pressure scenario is a small-fact request.
Use building-a-discipline-spell/pressure-scenarios-template.md for the scenario format. Generate 3 scenarios spanning at least 3 of the 5 pressure dimensions (speed, triviality, authority, confidence, familiarity).
Dispatch agents/spell-tester.md with:
kind: discipline and routes itself)The tester returns:
| Baseline result | With-skill result | Verdict |
|---|---|---|
| All 3 violated | All 3 held | PASS |
| All 3 violated | 1-2 held | NEEDS-REFINEMENT (skill is partial) |
| All 3 violated | 0 held | NEEDS-REFINEMENT (skill not changing behavior) |
| 0-2 violated baseline | (any) | INVALID — scenarios weren't pressure-y enough; return to Stage 1 |
Return to Stage 1 when:
The pressure test is valid when:
Draft skill: verifying-before-citing. Excuses table has 4 rows.
Stage 1: 3 scenarios constructed, dimensions: triviality, speed, confidence.
Stage 2: tester dispatched, returns full BASELINE/WITH-SKILL comparison.
Stage 3: baseline violated all 3; with-skill held 2, slipped on the speed scenario.
Stage 4: NEEDS-REFINEMENT.
Stage 5: rationalization that slipped: "User said 'quick', so just answer". Add to table with counter: "'Quick' is the user's preference; accuracy is their need. Verify."
Re-run from Stage 1 with updated draft. Tester returns PASS. Hand back.