Menu
Reflect on an existing breadboard by syncing it to code and surfacing structural smells before planning the next slice or refactor.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Read and write a Petri net (SDCPN) document by Automerge URL. Use when creating, editing, or querying Petri nets — adding or removing places, transitions, arcs, color types, differential equations, and parameters.
Create and maintain an Assumption Ledger — a persistent record of assumptions, their confidence, and validation status. Use when starting a new slice, resuming work in a new context window, or when implicit assumptions risk causing drift. Tracks requirements, architecture, and implementation assumptions.
Create or update a concept capsule — the conceptual anchor for a project or feature area. Use before writing code on a new project or feature, or when terms and boundaries feel unclear. Defines glossary, invariants, happy-path scenario, and non-goals.
Write a tracer-bullet card — a precise specification for one thin end-to-end slice of work. Use when scoping a new slice, defining what to build next, or breaking a feature into provable increments. Covers target behavior, boundary crossings, risks, and definition of done.
Create characterization tests (Golden Master) for existing code so you can refactor or replace safely. Use before refactoring, strangler-replacing, or modifying code with unclear behavior. Captures observable behavior with a minimal harness, producing tests, fixtures, and a coverage report.
Methodology triage consultant for tracer-bullet development. Use when unsure which pragma skill to run next, when starting a new project, or when the current approach feels stuck. Interviews the user, assesses state, and recommends the next pragma skill.
| name | shaping-breadboard-reflect |
| description | Reflect on an existing breadboard by syncing it to code and surfacing structural smells before planning the next slice or refactor. |
| argument-hint | [breadboard artifact and relevant code paths] |
Use this adjunct skill to reconcile breadboard artifacts with implementation reality, then identify design smells that affect planning.
Adopted from rjs/shaping-skills (breadboard-reflection) and adapted for this repository.
Modifications:
pragma:shaping-*characterize safety gate## Reflection Findings
- Sync fixes: [breadboard updates required]
- Smells: [specific boundary/name/wiring issues]
## Handoff To Pragma
- Safe planning follow-up: [`/pragma:card` or `/pragma:refactor`]
- Behavior uncertainty gate: [use `/pragma:characterize` before refactor when behavior is unclear]
- Next command: [single recommended pragma command]
/pragma:characterize first.stabilizing/pragma:consult (or /pragma:characterize when required)/pragma:consult