crucible

Coordinate release-hardening workflows across implementation, review, verification, and cleanup tasks.

6|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/GeekKingCloud/skills --skill crucible-geekkingcloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crucible
Source: https://github.com/GeekKingCloud/skills/tree/main/crucible
Command: npx skills add https://github.com/GeekKingCloud/skills --skill crucible-geekkingcloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually coordinating release-hardening tasks across implementation, review, verification, and cleanup is disjointed, error-prone, and often misses critical pre-release risks that could lead to production outages or security vulnerabilities.

Core Features & Use Cases

  • Sub-agent orchestration: Coordinate parallel implementation, review, and verification tasks across sub-agents for faster, more thorough hardening.
  • Iterative gate remediation: Run and iterate on Evidence Gate, Roast review, security, cleanup, and optional adjunct assessment gates until all actionable findings are resolved.
  • Evidence-backed reporting: Generate concise, release-readiness reports with clear evidence trails, unresolved risks, and exact next steps for blockers.
  • Use Case: When preparing a new feature for production release, use Crucible to take your implementation plan or full-project roast findings, coordinate fixes, run all required verification checks, and produce a clear report confirming the release is ready or identifying exact blockers.

Quick Start

Use the crucible skill to harden the current project for release using the full-project roast-led work queue.

Frequently Asked Questions about crucible

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate release hardening and security audit checks for production readiness?

Automate release hardening by orchestrating parallel sub-agents to run iterative evidence gates, security audits, and code reviews, producing a clear release-readiness report with exact blockers.

What is the best way to coordinate code review remediation and cleanup tasks before a release?

Coordinate code review remediation by using sub-agent orchestration to assign implementation and review tasks in parallel, then iterate on cleanup and verification gates until all findings are resolved.

Can I use sub-agent orchestration to manage security hardening for large codebases?

Yes, sub-agent orchestration applies to codebases of any size, delegating parallel security hardening and cleanup tasks across sub-agents to eliminate disjointed manual pre-release coordination.

How do I generate evidence-backed release readiness reports with unresolved risks?

Generate evidence-backed release readiness reports by running iterative gate remediation checks, which output concise reports containing clear evidence trails, unresolved risks, and exact next steps.

Does release hardening work with existing full-project roast findings and implementation plans?

Yes, release hardening workflows can take your existing implementation plan or full-project roast findings as input, coordinate necessary fixes, and run all required verification checks for production release.

When should I use automated evidence gates instead of manual pre-release security checks?

Use automated evidence gates when manual pre-release coordination becomes error-prone and disjointed, requiring iterative remediation for code quality, security, and cleanup checks to prevent production vulnerabilities.