oro

Use when reviewing a spec or task graph for completeness before implementation

Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions

Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions

Use when decomposing a spec, design, or feature description into a task dependency graph with self-evaluating acceptance criteria

Use when doing creative product, feature, component, functionality, or behavior design work

Use when infrastructure or features are built but before declaring done -- verifies work is wired into the system and actively used

Use when task completion or context usage requires a handoff readiness check

Use when ending a session, switching context, or needing to transfer work state to another session or agent

Use when about to run any git state-modifying command, file deletion, or irreversible operation

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

Use when a non-trivial problem has been solved and verified working -- captures the solution as searchable institutional knowledge

Use when executing tracked tasks through the full implementation lifecycle

Use when you have a written implementation plan to execute, with review checkpoints between tasks

Use when entering an unfamiliar codebase area, starting major work, or needing to understand architecture before making changes

Use when implementation is complete and all tests pass -- guides verification, integration options, and cleanup

Use when creating git commits -- determines type, scope, and message from staged changes

Use when interacting with GitHub issues, PRs, CI runs, or the GitHub API via the gh CLI

Use when about to edit code to fix a bug or change behavior -- check actual system outputs before making changes

Use when working in an oro-managed project, running an oro task, or launching the oro swarm

Use when evaluating a design decision or implementation plan before committing to it

Use when receiving code review feedback -- before implementing suggestions, especially when feedback seems unclear

Use when improving existing code structure without changing behavior, after tests are green

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

Use when starting a new session that continues previous work, or when a handoff document is provided

Use when code changes may require documentation updates or stale documentation review

Use when implementation phase is complete -- verifies code matches spec, identifies gaps, and tracks completion state

Use when the user asks about prior conversations, past sessions, or historical context not in current memory

Use when the user asks to make a spec, spec out work, or brainstorm a validated task graph

Use when encountering any bug, test failure, or unexpected behavior -- before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when you need an interactive TTY for REPLs, long-running processes, or orchestrating multiple coding agents in parallel

Use when designing, critiquing, or improving data visualizations -- applies Tufte's principles (data-ink, lie factor, chartjunk, small multiples) and implements them in seaborn

Use when starting feature work that needs isolation from the current workspace

Use when checking which skills apply before starting a task

Use when about to claim work is complete, fixed, or passing -- before committing, creating PRs, or marking tasks done

Use when running oro as a software factory and continuously observing, detecting defects, filing bug tasks, fixing via workers, and relaunching

Use when picking up a tracked task to execute end-to-end

Use when a user request arrives and the appropriate workflow or skill chain is not immediately obvious

Use when about to write or modify code in any project, before the first edit of a task

Use when you have validated requirements or a design and need a step-by-step implementation plan before writing code