osmani-harness-loop

星标0

分支0

更新时间2026年5月16日 11:15

Implementation of the 7-step Osmani Standard for Harness-Driven Development. Designed for autonomous, long-running agent loops.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

LaAbadIAdelCrimen

LaAbadIAdelCrimen/AbadIA-MCP

下载

The Osmani Harness Loop (7 Steps)

Designed for autonomous agents (e.g., Ralph-style scripts or long-running Hermes sessions) to ensure self-correction and continuous quality.

Identity & Context: Initialize with a clear mission and persona (e.g., Guillermo).
Anti-Rationalization: Declare assumptions and risks. Stop "agreeable hallucinations."
Harnessing (The Cage): Write the tests/constraints before the code.
Deterministic Execution: Build the solution using verified tools only.
Audit & Critique: Run a "Critic" loop on the output.
Distillation (The Ratchet): Extract permanent skills/knowledge from the session.
Sovereignty Check: Verify that the system is still under the user's defined "Harness."

Derived from the principles of Addy Osmani (2026).

同仓库更多 Skills

同仓库

Patrón de escalado de capacidad del modelo por subtarea — cuándo cambiar RALPH_MODEL_CAPABILITY en .ralph/.env

Metodología de planificación para el bucle ralph en AbadIA-MCP — granularidad, estructura de tareas y prerrequisitos

Estrategia para promover componentes compartidos en vault/components/ — cuándo emitir un fichero vs. anotar en pending-components.md

Patrón de 3 capas (Alcance, Criterios, Evidencias) para [juez] checkpoints en tasks de vault

Estructura modular del vault de AbadIA-MCP — separación server-core/server-map y orden de dependencias entre pasadas

Reglas universales al escribir ficheros en vault/ — frontmatter de provenance, bloques Evidence y prohibición de código fuente

name	osmani-harness-loop
description	Implementation of the 7-step Osmani Standard for Harness-Driven Development. Designed for autonomous, long-running agent loops.
category	software-development
version	1.0.0

Designed for autonomous agents (e.g., Ralph-style scripts or long-running Hermes sessions) to ensure self-correction and continuous quality.

Identity & Context: Initialize with a clear mission and persona (e.g., Guillermo).
Anti-Rationalization: Declare assumptions and risks. Stop "agreeable hallucinations."
Harnessing (The Cage): Write the tests/constraints before the code.
Deterministic Execution: Build the solution using verified tools only.
Audit & Critique: Run a "Critic" loop on the output.
Distillation (The Ratchet): Extract permanent skills/knowledge from the session.
Sovereignty Check: Verify that the system is still under the user's defined "Harness."

Derived from the principles of Addy Osmani (2026).