Goal-completion QA + fraud gate. Independently re-verifies delivered behavior against the goal's successCriteria, hunts edge cases and regressions, and hunts fake implementations (stubs, hardcoding, assertion theater); returns PASS or FAIL via a fixed C1–C12 checklist.
Binary contract critic (panel seat 1 of 3) — feasibility lens. Attacks a drafted ClarificationGoalContract against the real codebase and returns APPROVE or REJECT via a fixed C1–C6 checklist.
Binary contract critic (panel seat 3 of 3) — coverage lens. Verifies a drafted ClarificationGoalContract fully covers the user's request, contains no placeholders, and states only binary-decidable success criteria with adequate evidence; returns APPROVE or REJECT via a fixed C1–C6 checklist.
Goal-completion changed-code security gate. Reviews a goal's changed files and their immediate call boundaries as an attacker would; returns PASS or FAIL via a fixed C1–C7 checklist.
Interactive idea development through guided Q&A dialogue. This skill helps users clarify and develop their ideas by asking targeted questions, expanding on possibilities, and producing a structured markdown document capturing the essence of their thinking. Triggers: "brainstorm", "idea", "organize ideas", "I want to…
Use when a user's request is vague, ambiguous, or underspecified. Runs recon-first clarification — codebase exploration before questions, then one bundled question round with defensible defaults — and outputs a Goal Contract for the durable /goal runtime. Triggers on "I want to...", "I need...", "let's build...", "can…
Primary execution workflow for durable /goal runtime. Use when a Goal Contract is active or when the user asks to execute, continue, verify, or complete a goal.
Behavioral guardrails to prevent common LLM coding mistakes — enforces surgical changes, assumption verification, and scope discipline before and during implementation. Use when implementing features, modifying code, or when you notice yourself about to make changes without reading the existing code first.
Rob Pike's 5 Rules of Programming — a decision framework that prevents premature optimization and enforces measurement-driven development. Use when the user says "optimize", "slow", "performance", "bottleneck", "speed up", "make faster", "too slow", or any request to improve code speed/efficiency. Also use when you…
Review changed code for reuse opportunities, quality issues, and inefficiencies using three parallel review agents, then fix any issues found. Triggers when the user says "agentic-simplify", "clean up the code", "review the changes", or after goal implementation when code quality verification is needed.
Use when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first, failing-test-first debugging workflow before fixing.
Use when a user's request is vague, ambiguous, or underspecified. Explores the codebase first, then runs an iterative Q&A loop grounded in the findings until ambiguity is gone. Outputs a clear, well-scoped context brief so the user can plan sharply. Triggers on "I want to...", "I need...", "let's build...", "can you…