optimus-plan

Validate task specifications against project docs and reserve a git worktree branch.

Updated Apr 2, 2026

Search Tags:#worktree #workspace #plan #state-management #task-spec #optimus

Ready to run

npx skills add https://github.com/alexgarzao/optimus --skill optimus-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: optimus-plan
Source: https://github.com/alexgarzao/optimus/tree/main/plan/skills/optimus-plan
Command: npx skills add https://github.com/alexgarzao/optimus --skill optimus-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates a pending or in-progress task spec against project docs before implementation to prevent downstream rework and ensure alignment with requirements. This step also reserves a workspace by creating or preparing a development branch/worktree.

Core Features & Use Cases

Validates TaskSpec against project artifacts (PRD, TRD, API design, data model, coding standards) to detect gaps, contradictions, and missing test coverage.
Creates a workspace by deriving a canonical branch name and reserving a git worktree, updating state.json with status and branch information.
Provides recovery and collision-handling strategies for abandoned workspaces and pre-existing branches.

Quick Start

Run optimus-plan to validate the current or next task spec and reserve a workspace branch for development.

Frequently Asked Questions about optimus-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate a task spec against project docs before coding?▼

Validating a task spec against project docs requires checking the specification for gaps, contradictions, and missing test coverage against PRD, TRD, API design, and coding standards before implementation begins to prevent downstream rework.

What is the best way to prep a workspace and reserve a branch for a new task?▼

Prepping a workspace involves deriving a canonical branch name and reserving a git worktree for development. This process updates the project state with status and branch information to prevent collisions and prepare the environment.

How do I create a git worktree for a new development task?▼

Creating a git worktree involves deriving a canonical branch name and reserving it for development. The workspace is prepared by updating the project state with the new status and branch information to track progress.

Can I re-validate an in-progress task spec after updating project requirements?▼

Re-validating an in-progress task spec after updates executes hard checks against project docs to detect new contradictions or missing test coverage. This ensures the ongoing implementation remains aligned with the latest requirements.

How do I handle abandoned workspaces or pre-existing branch collisions?▼

Handling abandoned workspaces and pre-existing branch collisions requires recovery strategies that clear or reclaim the reserved git worktree. This ensures the canonical branch name is available for the current development task.