Software Development Skills

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 the user asks about their own past work or rules — "how did I deploy X", "why did I stop using Y", "what did we decide about Z", "do we have a rule/standard for W" — by searching the knowledge/ vault (standards first, then principles, then cases) before answering from general knowledge. Every retrieval must be logged to the retrieval log.

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 result came back surprisingly clean; or you cannot say in one sentence what done looks like. Also use when a task keeps failing or stalling, or when the user says "five gates", "five-gate method", "fable mode", "think like Fable", "slow down and do this right", or "think this through first". Loads a five-gate task loop (scope, evidence, adversarial reasoning, verification, calibrated reporting) plus standing habits. Model-agnostic - runs on any capable LLM.