crucible
SolidPressure-test important decisions, plans, proposals, strategies, architectures, and recommendations before acting. Use when trade-offs, uncertainty, meaningful downside, or an important second opinion could change the outcome. Stay lightweight for routine or trivial work.
Install
Quality Score: 85/100
Skill Content
Details
- Author
- smshahbaj
- Repository
- smshahbaj/crucible
- Created
- 6 days ago
- Last Updated
- 5 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
crucible
Assumption-driven venture validation that compounds founder judgment across sessions. Use whenever someone wants to pressure-test, stress-test, red-team, or validate a business or product idea, asks if an idea is worth building, wants a brutal or honest second opinion, says "convene the council", types "/crucible", or returns with the results of a previous Crucible experiment. Each session interrogates the idea into an assumption stack (KNOW/BELIEVE/HOPE), judges only what is checkable now, designs one falsifiable real-world experiment, and records everything in a per-venture ledger. The idea may be provided inline (e.g. "/crucible [the idea]").
crucible
The epistemic forge. Sits upstream of every other BrainStormer skill. Before you build, before you scaffold, before you ideate — CRUCIBLE forces you to enumerate what you actually know, what you're assuming, and what you can verify. Four phases: Pre-Flight (assumption enumeration), Architecture (falsifiable structure), Quality Gate (verification contracts), Evolution (compounding knowledge). This is the assumption-audit muscle promoted from debugging to default mode. Every skill, agent, feature, and design decision passes through CRUCIBLE's epistemic filter before resources are committed. Trigger on: "crucible", "epistemic check", "what do we actually know", "assumption audit", "prove it first", "verify before building", "falsifiability check", "pre-flight", "epistemic clarity", "what are we assuming", "challenge assumptions".
crucible
CRUCIBLE is an 8-agent code production pipeline built on Loop Engineering principles. It takes any coding task through Architect → Coder → Reviewer → Tester → Optimizer → Security Auditor → Documenter → Deployer before delivering production-ready, tested, optimized, secured, documented, and shippable code. A Loop Sentinel governs all feedback cycles with stagnation detection, progress thresholds, and a global step budget — the pipeline always converges or halts with a clear reason. Use CRUCIBLE for any task where quality, correctness, and production-readiness matter. Trigger whenever the user says: "build", "write", "code", "implement", "create a function / class / module / app / script / API / service", "refactor this", "I need code that does X", or invokes /crucible. Always prefer CRUCIBLE over a single-pass response when the task is non-trivial — more than ~30 lines, any business logic, any external integration. Also trigger on: "do this properly", "production-ready", "I want this reviewed", "build this ri