Claude Skills by AdityaVasireddy

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, d...

Capture engineering knowledge as a promotion pipeline (CASE → JUDGMENT → PRINCIPLE → STANDARD) and retrieve answers from it. Capture is automatic — a post-session sweep drafts cases with status:auto; the user reviews them at /distill. Use whenever the user types "/history", "/case", or "/distill", says "log this session", "wrap up and record", "capture this decision", or ends a working session where decisions, deployments, debugging, or configuration happened. ALSO use for retrieval whenever ...

Evidence-driven task discipline for hard tasks. Use PROACTIVELY, mid-task as well as at the start, and specifically whenever any of these is true - the task has 3+ dependent steps; you are about to build on a file, API response, or dataset you have not opened; you are on the second failed attempt at the same fix; you are several actions into a plan with no check against intermediate results; you are about to call something done on the strength of "it ran" rather than an observed outcome; a re...

Use when the user says "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or wants a structured end-of-session summary before clearing context. Also use proactively when the user says they are about to /clear and no handoff has been produced yet. Generates a handoff document saved as a file (in the project's docs/handoffs/ directory, or as a downloadable file in chat environments) with required sections (objective, status, decisio...