suzbot

Implement an already-planned feature, step, or task. Validates the plan against architecture patterns, then executes with TDD and human testing checkpoints. Trigger phrases: 'implement the next step', 'build the next feature', 'start development' or similar.

Discuss and refine a feature, step, or task — whether part of a phase plan or stand-alone. Enforces discussion-first and produces a step spec with TDD and human testing checkpoints. Trigger phrases: 'refine the next step', 'discuss the next feature', or…

Post-feature reflection to identify process changes that reduce future friction and context overhead. Run after a feature is marked complete, or mid-session when the user wants a process check-in.

Run the [TEST] checkpoint sequence: present test items, wait for confirmation, route issues to /fix-bug. Invoked by /implement-feature at each [TEST] milestone.

Quick documentation lookup for how game systems work. Trigger phrases: 'remind me', 'how does X work', 'what does X do', 'refresh me on X'.

Start planning a new development phase. Reads requirements, facilitates discussion, and creates the phase design document.

Update project documentation after feature implementation. Use at [DOCS] checkpoints or when asked to update docs.

Investigate and fix bugs or gaps surfaced during human testing. Evidence first, agree on the problem, scan siblings, then fix. Trigger phrases: 'fix bug', 'investigate issue', 'something went wrong', or any problem/issue report during a [TEST] checkpoint.

Guide the tech design discussion and design doc drafting for a feature. Use when starting steps 3-4 of the feature process.

Update project documentation after feature implementation. Run at the end of a feature, phase group, or when asked to update docs.

Post-feature reflection to identify process changes that reduce future friction and context overhead. Typically invoked from /nq-update-docs at the end of a significant feature, or directly by the user for a mid-session check-in.