Convert agreed goals, constraints, and success criteria into a Seed specification an agent can execute and verify. A quality review checks consistency and testable outcomes, with any suggested refinements left for the user to approve.
Find the Ouroboros command for clarifying requirements, running work, checking results, or managing sessions. This reference explains command purposes, agent roles, natural language triggers in Claude Code, and the tools each operation requires.
Manage Ouroboros settings through a browser interface or chat commands. Choose agents and models globally or for individual stages, change the LLM backend, review saved settings, and restore the configuration from before the last change.
Turn a multi-file development task or technology migration into a specification with acceptance criteria, then launch background implementation and verification. The workflow clarifies missing requirements, reviews the specification, and tracks progress and blockers through linked jobs.
Find running or paused Ouroboros sessions after an MCP server disconnect. The skill lists saved sessions and provides commands to inspect recorded events, open a monitor, or resume execution with the original Seed specification file.
Turn a Seed specification into GitHub issues for team planning. The skill creates a parent issue and implementation tasks, distributes acceptance criteria across them, and links the tasks in a progress checklist.
Learn Ouroboros through a short, hands-on interview about your own project idea. Turn your answers into a sample specification with goals, constraints, and checkable outcomes, then learn the commands for execution, evaluation, and next steps.
Register and search existing Git repositories and worktrees, then choose which projects Ouroboros interviews use as context. You can also generate a configuration containing verified build, test, and other check commands for the evaluation workflow.
Execute an existing Ouroboros Seed, a specification containing a goal and acceptance criteria, as a background job. The workflow checks each criterion, normally queues formal evaluation, and follows a bounded improvement loop if evaluation rejects the result.
Stop stuck Ouroboros executions or background jobs by ID, or cancel all running and paused executions in the current project. It reports whether cancellation is complete or has been requested, with guidance for checking the final status.
Verify finished work against acceptance criteria using executable checks and a review of whether each requirement is met. Multiple models can review uncertain cases, and rejected work can enter an automated repair loop when the required Seed is available.
Start and monitor an Ouroboros development loop that revises project concepts and acceptance criteria, the conditions for judging completion. Run and evaluate successive generations, focus revisions on failed criteria, inspect progress, or rewind to an earlier generation.
Turn a vague development idea into clear goals, constraints, and acceptance criteria through a guided interview. It checks unresolved decisions and confirms the agreed goal before moving toward a Seed, the requirements document used by Ouroboros.
Start the introductory guidance for Ouroboros by sending `ooo` or asking to begin. This entry point passes control to the welcome skill, including before runtime-specific setup has been completed in the Marketplace plugin.
Turn a product idea into a product requirements document through guided questions. Review existing system behavior and measurements as evidence, confirm how answers are recorded, and keep decisions separate from assumptions and unresolved items.
Check code, documents, API responses, and other outputs against a defined quality bar. Receive a score, a pass, revise, or fail verdict, and practical suggestions, with observed behavior informing checks where applicable tools are available.
Run repeated Ouroboros execution and improvement cycles as a background job, starting from a Seed specification or continuing an existing lineage. The loop stops on a quality check pass, convergence, cancellation, or the generation limit, and reports the outcome.
Set up Ouroboros inside Claude Code with a guided wizard. Check runtime requirements, configure the Claude runtime, optionally add project instructions to CLAUDE.md, and register existing repositories as context for future interviews.
Check an Ouroboros execution session’s status and progress, and optionally compare its current output with the original Seed specification. The drift report explains goal deviations and suggests whether to continue, evaluate, or reconsider the direction.
Work through repeated failed fixes or difficult technical choices using five perspectives: practical action, missing information, simplification, architecture, and challenged assumptions. Compare alternatives and disagreements, then receive a recommendation while keeping the final decision with the user.
Check whether an Ouroboros update is available and upgrade after the user chooses to proceed. The native updater preserves the installation manager, environment, and optional dependencies, then provides restart guidance for the host integrations.
Get started with Ouroboros through an interactive introduction that checks setup readiness and asks about your goals. Learn the core commands, then move into a project interview, a tutorial, or the help reference.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)