jpicklyk/task-orchestrator

API Compatibility Review assesses changes to MCP tools and REST endpoints separately for compatibility notes. Use it when a change may affect parameter schemas, response shapes, or documentation updates.

Adopt Project Scope migrates an existing unscoped Task Orchestrator database to project scoping in place. It creates or attaches a project root, re-parents existing work trees, and writes the root UUID to config.yaml when setting up a workspace for multiple projects.

Batch Complete closes out or cancels multiple items in a task tree. Use it to finish a feature subtree, clean up old work, or archive completed workstreams.

Configure Server decides how the MCP Task Orchestrator container runs and is reached, including HTTP vs STDIO, REST API mode, port publishing, config mounts, and config-sync. Use it when reconfiguring the server, exposing the API, or switching endpoints.

Create Item turns conversation context into a tracked MCP work item. It anchors bugs, features, tech debt, and observations in the right container, infers priority, and can create single items or work trees.

Dependency Manager visualizes, creates, and deletes BLOCKS-style dependencies between MCP work items. Use it to see what blocks an item, link items, remove edges, or diagnose why work cannot start.

Feature Implementation guides a feature-implementation item from queue through work and review. It creates or resumes the feature container, fills required notes, dispatches child tasks, and advances the item to terminal state.

Implement takes MCP work items from backlog to merged PR. It handles branching, schema-driven planning, implementation, review, and PR creation when you need to pick up a task or fix bugs.

Manage Schemas creates, views, edits, deletes, and validates note schemas in `.taskorchestrator/config.yaml`. It also helps design workflow gates and configure actor authentication for the MCP Task Orchestrator.

Migration Review evaluates SQLite schema changes for safety, including table recreation, data backfills, foreign key ordering, and Flyway migration correctness. Use it when filling migration-assessment notes for items tagged needs-migration-review.

Performance Review evaluates whether a change affects hot paths, query patterns, serialization cost, and overall complexity. Use it when preparing performance-baseline notes for a Kotlin MCP server with SQLite.

Plugin Impact Review assesses which skills, hooks, and docs need updates after MCP, config, or output-shape changes. Use it when filling plugin-impact notes and checking cached hook or skill references.

Post-Plan Workflow materializes approved plans into MCP items, wires dependencies, and dispatches implementation agents. Use it after plan approval to move from planning into execution and verification.

Pre-Plan Workflow gathers existing MCP items and schema requirements before planning. Use it when entering plan mode to avoid duplicate work and account for required notes and gates.

Prepare Release automates an end-to-end release flow: it reviews commits since the last tag, drafts a changelog, creates and merges a release PR, tags the release, and watches the Docker build finish. Use it when preparing a new version after feature work lands.

Quick Start orients users to the MCP Task Orchestrator by detecting workspace state and explaining plan mode, persistent tracking, and project scoping. Use it when you want a first-time walkthrough or need to understand how the pieces work together.

Ralph launches the queue drain script and emits the exact `node ralph-loop.mjs` command for a chosen filter and bounds. Use it to preview what will be processed before running the separate loop process.

Review Proposals triages pending improvement-proposal MCP items, shows their scope and evidence, and records accept, reject, defer, or skip decisions. It also applies project-scoped YAML changes or files a global issue when a proposal is accepted.

Review Quality verifies implementation work before it is marked complete. It checks plan alignment, test coverage, and code simplification during the review-to-completion gate.

Schema Workflow drives schema-tagged MCP work items through gate-enforced phases and fills required notes from runtime schema guidance. Use it when an item matches configured work-item or note schemas and must be advanced step by step.

Session Retrospective analyzes an implementation run by checking schema quality, delegation alignment, note effectiveness, and plan-to-execution fit. Use it after a run or when you want a session review and improvement notes.

Spec Quality Framework defines the minimum analysis a plan must include: alternatives, non-goals, blast radius, risk flags, and test strategy. Use it when filling queue-phase specification notes for MCP work items.

Status Progression shows the current role, gate status, missing notes, and the correct trigger for advancing a WorkItem. Use it to move, block, resume, cancel, or complete items with advance_item.

Test Authoring Framework separates test planning from implementation by deriving scenarios, oracle sources, and probes from acceptance criteria. Use it when filling test-plan or test-manifest notes, or when reviewing tests for implementation independence.

Work Summary generates a compact dashboard from MCP work items, showing what is active, blocked, next, and queued. Use it at session start or when asking for project status, backlog, or where to resume work.