メニュー
Unified entry point for feature work. Classifies work type, checks for existing state, pours the right molecule. The user says "build X" and the system handles the rest.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when adding or modifying a hook, gate, denial/permission message, or waiver/exemption/override path; when deciding whether to keep, revise, or retire a rule or gate; or when auditing a gate or triaging a complaint that a gate causes friction. The implementation manual for building gates that are enabling not coercive — escape paths, persistent signal, value-not-presence validation, with audit-validated reference designs and anti-patterns.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
| name | build |
| description | Unified entry point for feature work. Classifies work type, checks for existing state, pours the right molecule. The user says "build X" and the system handles the rest. |
Optional explicit trigger for the mol-feature pipeline. Claude should also auto-detect build intent per planning-discipline.md — this skill exists for when the user wants to be deliberate.
/build {description of what to build}
Classify — Is this a feature, bug, chore, or spike?
Check existing state — Don't duplicate work.
bd mol current — active molecule already?bd list — existing tasks for this topic?openspec/changes/ — existing change?Pour the right molecule:
bd mol pour mol-feature --var name="{name}" --var problem="{problem}"
Or mol-rapid for bugs/chores.
Step back — molecule-awareness drives the pipeline from here.
"Starting {name}. First up: does this need building?"
Then the brainstorm step runs. The user never sees molecule IDs, formula names, or bd commands.
.beads/ Directory?Initialize beads and Claude integration automatically:
bd init
bd setup claude
Then proceed with the molecule pour as normal. The user should not have to
set up beads manually — /build handles it.