/crucible
Reads the codebase first with path:line facts, applies the skip/reuse/stdlib/minimal ladder, evaluates five axes, and asks at most 3 open design-changing questions per batch.
npx skills@latest add luci-efe/skills -s crucible- DecideStage
- 06 Autonomy with ownershipMethod
- .ramos/
decisions/ <topic>.mdProduced artifact / output
Use when
A feature, refactor, or design is underspecified or has competing approaches before writing code.
Support & adapters
- Instructions usable across harnesses
Decision tree
- 01→ Code-settled facts recorded
Step 1: Read first (no questions yet)
Write what the code already decides as facts with path:line
- 02→ No speculative abstractions
Step 2: The ladder
1. Skip/
delete? → 2. Already in repo? → 3. In stdlib/ existing dep? → 4. Minimal new code - 03→ Settled, assumed, or answered axes
Steps 3–4: Five axes & open questions
Check Scope, Data/
state invariants, Failure modes, Security/ trust boundaries, Verification proof; ask max 3 questions per batch - 04→ .ramos/
Step 5: Record decision file
Write .ramos/
decisions/ <topic>.md with Facts, Ladder outcome, Axes table, Out of scope, and Proof command decisions/ <topic>.md
Prerequisites & install recipes
- rgrequired · default branch
rgbrew install ripgrep
Completion criteria
- Every axis (Scope, Data/
state invariants, Failure modes, Security/ trust boundaries, Verification proof) is settled, assumed, or answered. - Asks at most 3 questions per batch, each with a recommended answer and trade-off.
- Writes .ramos/
decisions/ <topic>.md naming the exact command(s) / proof will run.
Want something like this built for your company?
Book a callMessage me on LinkedInSee Agentic Engineering