Optimus
Skills marketplace for Droid (Factory), Claude Code, and OpenCode.
Requires the Ring ecosystem (droids + pre-dev workflow).
Task Lifecycle
Skills are classified as Administrative (run anywhere) or Execution (require feature branch).
Administrative Skills
| Skill | Description | Command |
|---|
import | Import Ring pre-dev artifacts into optimus format. Creates optimus-tasks.md with TaskSpec column. Re-runnable — only imports what's new | /optimus-import |
report | Task status dashboard. Shows progress, active/blocked/ready tasks, dependency graph, and parallelization opportunities. Mostly read-only — only writes .optimus/config.json defaultScope when user opts in | /optimus-report |
tasks | Administrative: Create, edit, remove, reorder, cancel, and reopen tasks. Manage versions and move tasks between versions. Runs on any branch | /optimus-tasks |
batch | Pipeline orchestrator: chains stages 1-4 for one or more tasks with user checkpoints between stages | /optimus-batch |
resolve | Administrative: Resolves merge conflicts in optimus-tasks.md caused by parallel task execution across feature branches | /optimus-resolve |
resume | Administrative: Resume a task after closing the terminal. Locates/recreates the worktree for a given T-XXX, reports current status, and offers to invoke the next stage. Read-only on state.json except for a user-confirmed Reset-to-Pendente recovery. | /optimus-resume |
quick-report | Compact daily status dashboard. Shows version progress, active tasks with current status, ready-to-start, and blocked tasks. Mostly read-only — only writes .optimus/config.json defaultScope when user opts in | /optimus-quick-report |
help | Lists all available Optimus skills with descriptions, usage commands, and when to use each one | /optimus-help |
sync | Sync all Optimus plugins — install new, update existing, remove orphaned. Recommended after new releases | /optimus-sync |
Execution Skills (stages 1-4)
Stage-1 creates the workspace (worktree). Stages 2-4 auto-navigate to the task's worktree.
Pendente → Validando Spec → Em Andamento → Validando Impl → DONE
(plan) (build) (review) (done)
| Skill | Stage | Description | Command |
|---|
plan | 1 | Validates task specifications against project docs before implementation. Catches gaps, contradictions, and test coverage holes. Creates workspace (branch/worktree) | /optimus-plan |
build | 2 | End-to-end task implementation with verification gates, code review, and commit approval | /optimus-build |
review | 3 | Validates completed task implementation against spec, coding standards, and best practices using parallel specialist agents | /optimus-review |
done | 4 | Requires PR in final state (merged or closed) before marking task done. Cleans up worktree and branch interactively | /optimus-done |
Conventions
Optimus uses Conventional Commits 1.0.0 end-to-end — derived automatically from each task's Tipo column:
| Tipo | Prefix | Branch | Commit / PR title |
|---|
Feature | feat | feat/t-003-user-auth | feat(T-003): add login API |
Fix | fix | fix/t-007-duplicate-login | fix(T-007): debounce submit |
Refactor | refactor | refactor/t-012-... | refactor(T-012): ... |
Chore | chore | chore/t-015-... | chore(T-015): ... |
Docs | docs | docs/t-018-... | docs(T-018): ... |
Test | test | test/t-021-... | test(T-021): ... |
Branch names, commit messages, and PR titles are all derived from the same Tipo — no manual mapping needed. build validates PR titles against the Conventional Commits regex and offers to fix non-conforming titles via gh pr edit. Structural edits to optimus-tasks.md (new task, dependency edit, version move) always use chore(tasks): regardless of the affected tasks' Tipo.
Full spec: AGENTS.md — Conventional Commits and Branch Name Derivation.
Review & Verification Skills
