ooo

Run a spec-first loop with immutable seeds and drift verification.

40|9|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/akillness/jeo-skills --skill ooo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ooo
Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/ooo
Command: npx skills add https://github.com/akillness/jeo-skills --skill ooo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ouroboros provides a spec-first loop that reduces ambiguity by conducting a Socratic interview and freezing an immutable seed before execution, enabling continuous refinement until verification.

Core Features & Use Cases

  • Spec-first interview: clarify requirements before coding.
  • Seed-Then-Execute: freeze contract and run against it with drift monitoring.
  • Verify-Then-Continue: loop until acceptance criteria are met across iterations and evolve when ontology changes.

Quick Start

Start an interview to freeze the seed and then run the workflow to verify completion.

Frequently Asked Questions about ooo

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

FAQPage Schema
How do I reduce ambiguity in software requirements before execution?

A spec-first workflow reduces ambiguity by conducting a Socratic interview to clarify requirements and freezing an immutable seed before execution. This ensures continuous refinement and verification until acceptance criteria are met.

How do I measure drift against an immutable spec during iterative development?

You measure spec drift by freezing an immutable seed and running a spec-first loop with continuous drift monitoring during execution. The workflow evaluates iterations against the frozen contract, ensuring verification before completion and evolving only when ontology changes.

What is the best way to verify outcomes across iterative development cycles?

The best way to verify outcomes across iterations is using a verify-then-continue loop that evaluates each execution against a frozen seed. This ensures acceptance criteria are met before proceeding and triggers an evolution phase if the ontology changes.

When should I use a spec-first loop instead of standard execution workflows?

You should use a spec-first loop when your project requires strict immutable specs, drift measurement, and verification before completion. It is ideal for iterative processes where requirements need continuous refinement and evaluation against a frozen contract before evolving.

How do I start a spec-first workflow to freeze a contract?

To start a spec-first workflow, you initiate an interview phase to define a clear, verifiable seed. Once the interview clarifies the requirements, you freeze the seed into an immutable contract and begin execution with drift monitoring and verification.