warpx

Write an implementation plan as a markdown file, then immediately serialize it to a timestamped YAML task file in .ctx/tasks/. Use before touching any code when given a spec or approved design.

Design-first workflow for new features, components, or architecture decisions. Use before writing any code — get explicit approval on a design first.

Commit-and-push workflow with validation. Use when asked to "cap", "commit and push", or "ship it".

Systematic debugging for Rust. Use before proposing any fix — establish root cause first, then write a failing test, then fix.

Dispatch parallel subagents for independent tasks. Use when 2+ tasks have no shared state or sequential dependencies.

Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items.

Test-driven development workflow for Rust. Use before writing any implementation code — write a failing test first, then implement, then refactor.

Verification gate before claiming any work is complete. Use before committing, creating a PR, or reporting "done".

Session-end handoff writer. Use at end of a session to update HANDOFF.yaml with completed work, new gaps, and current project state.

Session-start handoff reader. Use at the start of a session to orient to outstanding work — scans for HANDOFF.yaml, triages items by priority, and acts accordingly.

Close the session — write handoff state and summarize what was accomplished.

Orient to the current repo at session start — handoff items, overdue todos, and next godmode task.

Show the current task graph and next runnable task for this repo using godmode.

Morning and end-of-day rituals for development sessions. Handles orientation (handon), status checks, handoff writing, and daily note updates. Use at session start or end.

Senior dev companion that handles design, debugging, refactoring, and ad-hoc development work. Auto-routes to code review, architecture exploration, or workflow orchestration as needed. Use when starting any substantial development task, investigating bugs, or refactoring code.

Structured code review for the current diff or specified files. Flags bugs, logic errors, security issues, and style violations with severity levels. Use before committing, before PRs, or when reviewing changes.