xcaeser

work

Accountable lead for free-form implementation work: define the exact result, choose a bounded and evidence-driven agent team, integrate changes, and prove completion. Use when the user asks Work to build, fix, implement, or change something without selecting a dedicated Work mode.

work-audit

Evidence-first, read-only audits that always use one gpt-5.6-sol xhigh analyst and return a self-contained fix plan suitable for a lower-capability execution model. Use when the user asks to audit code, a diff, a branch, an artifact, or a runtime flow.

work-checklist

Turn the current implementation concerns into a prioritized checklist, register one concrete goal, and work through every item until it has a proven disposition. Use when the user wants to convert concerns into an execution checklist and make the application more robust.

work-clean

Read-only code-simplification analysis that always uses one gpt-5.6-sol xhigh analyst and returns a self-contained cleanup plan suitable for a lower-capability execution model. Use when the user asks to clean code, remove smells, reduce overengineering, refactor helpers, or assess package choices.

work-concern

Inspect the current implementation and surface a short list of concrete, evidence-backed concerns without editing or producing a full audit or fix plan. Use when the user asks what gives you pause, what might be wrong, or wants a lightweight implementation sanity check.

work-help

Show the separate Work skills and their purpose without running a task. Use when the user wants to remember how Work is organized or asks what Work skills are available.

Code & Development Listed

work-ideate

Run an interactive, rigorous ideation session that turns a vague desire into a sharp problem, distinct options, and a testable next move. Use when the user wants to brainstorm a product, feature, business, creative, architecture, or project idea; refine a direction; compare options; or be challenged by a thoughtful creative sparring partner.

work-init

Guide and verify a minimal new project setup by asking only essential questions about project type, language, runtime, platforms, packages, and validation. Use when the user wants to start a new project.

work-plan

Turn a task into a detailed, read-only execution plan by always launching one gpt-5.6-sol xhigh analyst and producing a self-contained handoff suitable for a lower-capability execution model. Use when the user wants a plan before implementation.

work-quality

Pass the Work golden rules directly into the current conversation without spawning agents, editing files, or changing project state. Use when the user asks for the quality bar, taste principles, or a ready-to-paste software standard.

Testing & QA Listed

work-test

Inspect a codebase and write a small number of high-value tests for real, observable behavior using the repository's existing framework and conventions. Use when the user asks to add, improve, or write meaningful tests without optimizing for coverage.

work-status

Show a read-only snapshot of the current Work goal, checklist, agents, evidence, blockers, current step, and next parent action. Use when the user asks for Work status.