Menú
Mandatory quality gate for every Issue, Milestone, and PR with zero-error execution and no technical debt carry-over.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Rules and strategies for managing agent context window size, avoiding bloat, and preserving signal-to-noise ratio.
Standard patterns for error handling, retry logic, circuit breakers, and graceful degradation.
Detect and remove contradictions across agent policies before execution.
Multi-step tool workflows via code orchestration to reduce latency, context pollution, and token overhead.
Bind project-specific prompts to local schema and workflow artifacts while keeping the harness core generic and globally reusable.
Operational session protocol for task-scoped leases, reconciliation, checkpoints, inspection, queue promotion, and handoff across long-running work.
| name | completion-gate |
| description | Mandatory quality gate for every Issue, Milestone, and PR with zero-error execution and no technical debt carry-over. |
Enforce a mandatory quality gate for every Issue, Milestone, and PR with zero-error execution and no technical debt carry-over.
done/merge.When using the harness-lifecycle pattern, an additional rule applies:
A feature is only
"passes": trueinfeature_list.jsonif a real test execution (unit, integration, or e2e) confirms it works. Code review alone is insufficient. The agent must have run the tests, not just inspected the code.
testing-policy — defines the required test layers (unit/integration/E2E/non-regression) that must pass during this gateharness-lifecycle — defines the two-phase lifecycle that uses this gate for feature verification