withakay

Implement Ito Lite markdown changes by reading proposal/spec/design/tasks artifacts and updating manual task statuses. Use when applying or executing a prompt-only Ito Lite change without the ito CLI.

Archive completed Ito Lite changes by manually merging spec deltas into current specs and moving the change to archive. Use after implementation and verification when no ito CLI is available.

Create prompt-driven Ito Lite change proposal packages in markdown. Use for drafting proposal.md, spec deltas, optional design.md, and tasks.md without the ito CLI or validation executable.

Review Ito Lite markdown proposal packages before implementation. Use to check proposal.md, spec deltas, design.md, and tasks.md for consistency, risk, testability, and manual validation without the ito CLI.

Initialize a markdown-only Ito Lite workspace with no executables. Use when setting up prompt-driven change proposals, creating .ito-lite/project.md, or preparing a repo for Ito-style specs, changes, and tasks without the ito CLI.

Coordinate the prompt-only Ito Lite workflow for proposals, specs, tasks, reviews, implementation, and archive without the ito executable. Use when the user asks for Ito-style planning, change proposals, lightweight specs, or markdown-only change management.

Balanced skill for typical development tasks, code review, and implementation work

Coordinator-only agent for orchestrating multi-change runs

Build reproducible Showboat demo documents that prove repo behavior with executable markdown. Use when asked to create demos, proof-of-work walkthroughs, or verification artifacts with showboat, especially for tests, CLIs, local services, Aspire AppHosts, and HTTP APIs.

Build reproducible Showboat demo documents that prove repo behavior with executable markdown. Use when asked to create demos, proof-of-work walkthroughs, or verification artifacts with showboat, especially for tests, CLIs, local services, Aspire AppHosts, and HTTP APIs.

Balanced skill for typical development tasks, code review, and implementation work

Coordinator-only agent for orchestrating multi-change runs

Fast, cost-effective skill for simple tasks, quick queries, and small code changes

Read-only researcher for Ito orchestration context gathering

High-capability skill for complex reasoning, architecture decisions, and difficult problems

Implements Ito orchestration work packets and remediation tasks

Manage remote Kocao agent sessions from an AI assistant. Use when: listing running agents, starting a new remote agent, checking agent status, viewing agent logs, stopping an agent session, or sending a prompt to a running remote agent.

Fast trigram-indexed code search across the entire repository using Zoekt (the engine behind GitHub and Sourcegraph code search). Use INSTEAD OF grep/ripgrep for broad codebase searches. Supports regex, literal strings, file filters, and symbol queries. Auto-installs zoekt binaries and auto-indexes the repo on first use.

Apply a Change Proposal. Triggered by the user saying "Apply change <change-id>" or "Implement change <change-id>". Use when implementing, executing, applying, building, coding, or developing a feature, change, requirement, enhancement, fix, or modification. Use when running tasks from a spec, proposal, or plan.

You MUST use this before any creative work - creating features, proposing changes,building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — presents structured options for merge, PR, or cleanup

Run an ito ralph loop for a specific change (or module/repo sequence), with safe defaults and automatic restart context on early exits.

Use when creating and writing an Ito change proposal (new change or existing change id). Delegates to Ito CLI instruction artifacts.

Use when executing implementation plans with independent tasks in the current session using subagents

CLI for the Renzu MCP server. Call tools, list resources, and get prompts.

Use when implementing, executing, applying, building, coding, or developing a feature, change, requirement, enhancement, fix, or modification. Use when running tasks from a spec, proposal, or plan.

You MUST use this before any creative work - creating features, proposing changes,building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Create atomic git commits aligned to Ito changes. Use when you want to commit work after applying a change, optionally with auto-mode.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Review and validate Ito changes, specs, or implementations. Use when the user wants a quality check, code review, or validation of project artifacts.

Build and maintain an LLM-owned markdown wiki inside a repository. Use when setting up a repo wiki, scaffolding a wiki root, refreshing wiki pages from repo sources, ingesting new sources, answering from the wiki, or linting for gaps, stale content, and missing cross-links.

Create or update a project's `Makefile` with standard developer targets. Use when the user asks for a Makefile, wants `make build`, `make test`, `make run`, `make check`, or `make help`, or wants plain `make` to print help by default. Inspect the repo first and wrap existing project commands instead of inventing a new workflow.

Pull GitHub PR review threads and conversation comments via the gh CLI, triage them into verified fixes, implement changes, push updates, and optionally resolve review threads or minimise outdated comments; also poll every 4 minutes (sleep 240) up to 3 times for new feedback.

Respond to and address PR review comments. Fetches PR context, tracks resolution progress, and supports a workflow for systematically addressing reviewer feedback with agent assistance.

Build reproducible feature demos as markdown documents using showboat and Rodney browser automation. Use when the user asks for a demo, walkthrough, proof the UI works, screenshots of a feature flow, or an executable markdown artifact showing what was built.

Run a local Claude Code PR ultrareview using the repository prompt and Claude CLI, then triage the returned findings and fix valid issues. Use when the user asks for a Claude ultrareview, local ultrareview, unpaid ultrareview-style review, Claude CLI review of a PR, or asks to replace paid/cloud ultrareview with a local workflow.

Use when the user asks to clean, prune, or tidy git worktrees, or when worktree count seems excessive, or stale audit-mirror temp worktrees are accumulating.

Fast trigram-indexed code search across a repository using Zoekt. Use instead of grep/ripgrep for broad codebase searches. Supports regex, literal strings, file filters, and symbol queries. Auto-installs zoekt binaries and uses a local index on first use.