Grounding
Understand the problem before solving it. These skills ensure you're working on the right thing.
/aim
Clarify the outcome you want—a change in user behavior, not a feature shipped. The aim IS the abstraction. Start here to know what you're solving for.
/problem-space
Map what we're choosing to optimize and what constraints we treat as real. The problem space is the terrain where solutions live—get it wrong and you'll optimize the wrong thing.
/problem-statement
Frame the specific problem you're solving. Change the statement, change the solution space. A good problem statement opens possibilities; a bad one closes them prematurely.
Execution
Build and ship. Move from understanding to working software in users' hands.
/solution-space
Explore candidate implementations. Fan out cheaply, score against constraints, prune hard. Four levels of response: Band-aid (patch symptom), Local optimum (optimize current framing), Reframe (question the problem), Redesign (eliminate the problem).
/execute
Do the work. The terraform loop: Pre-flight (check orientation), Execute (build), Detect drift (watch for scope creep), Salvage (if drifting), Update terrain (encode learning). Steer or Abort—never thrash.
/ship
Deliver to users. Optimize the delivery path—the path from merged code to working install. When execution is cheap, delivery is the work. Reduce delivery-path tax: review-to-merge time, merge-to-prod time, manual approvals.
Reflection
Capture learning that compounds. Challenge assumptions. Extract wisdom before restarting.
/review
Check work and detect drift. Invokes metacognitive review to catch scope creep, over-engineering, incomplete implementations, and strategic misalignment. A second opinion before committing.
/dissent
Structured disagreement mode. Deliberately seek contrary evidence and alternative framings. Useful for avoiding confirmation bias and groupthink on important decisions. "What would make this wrong?"
/salvage
Extract learning before restarting. Code is a draft; learning is the asset. Captures what changed your model, what guardrails should exist, what context was missing. Then restart clean.