메뉴
Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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-discipline-spell |
| description | Use when the meta-builder routes to kind=discipline. Generates a discipline spell with the rule, excuses table, warning signs, and hard gates. |
| kind | workflow |
| audience | anyone |
| ai-tools | any |
| complexity | guided |
| time | 15-25 min |
| version | 1.0.0 |
| source | bundled |
Specialist builder for kind: discipline spells. A discipline is a non-negotiable rule the agent (or the user) keeps slipping on. This skill produces a SKILL.md tuned to enforce the rule against the agent's own rationalization.
building-a-spell Stage 2 when kind: disciplineA draft SKILL.md with all required discipline sections, ready for pressure-testing-a-spell to harden.
This is a workflow chain. Stages are explicit.
If the rule has any of these words, push back: "should", "try to", "consider", "when possible", "usually". A discipline rule is a hard rule.
Re-write the rule until it's:
Ask the user (or extract from prior turns):
Capture verbatim. Don't paraphrase. Aim for 4-6 excuses.
For each excuse, write the counter — sharp enough to actually stop the action.
What patterns in the agent's own reasoning would predict the rule is about to break? Examples:
These warning signs let the agent self-detect.
Identify the latest possible moment in the workflow where the rule could be enforced. Place a <MUST-STOP> block there with explicit "if this isn't true, STOP" language.
Discipline skills have ONE gate, placed late. Multiple gates dilute the effect.
pressure-testing-a-spellHand off the draft to pressure-testing-a-spell. That skill orchestrates the discipline-mode tester (which runs the baseline + with-skill comparison).
If the tester returns NEEDS-REFINEMENT, the typical fixes are:
Return the PASSing draft. Meta-builder takes over for save.
<MUST-STOP> gate in the bodyReturn to Stage 2 when the tester finds a rationalization not in the table. Return to Stage 4 when the gate is being rationalized past. Return to Stage 1 when the tester finds the rule itself is too soft to enforce.
The draft is good enough when:
<SUBAGENT-STOP> at top to prevent recursive enforcementSee skills/building-a-spell/examples/example-discipline.md for a full walkthrough of building verifying-before-citing.