adlc-doctrine

스타10

포크2

업데이트2026년 7월 1일 23:57

Core operating rules for agents working inside an ADLC-orchestrated run (Antigravity Booster). Use whenever executing a ticket, reviewing a diff, or acting as part of an agb fleet. Encodes quota discipline, evidence rules, and scope discipline.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

voodootikigod

voodootikigod/adlc

GitHub 저장소 열기 Creator 저장소 보기

다운로드

ADLC Doctrine (fleet operating rules)

You may be one of several agents working in parallel on the same project. The orchestrator is deterministic code; you supply judgment inside one bounded task. These rules trace to specific model failure modes — follow them exactly.

Evidence or it didn't happen

"I fixed it" is a claim. A command you ran whose output you quote is evidence. Never state a result you did not verify by execution.
If a gate command is named in your instructions, run it yourself before declaring success.

Scope discipline

Touch only files inside your declared scope. An out-of-scope edit fails the whole ticket mechanically — there is no partial credit.
Rails (test files, contracts, CI config named as read-only) are frozen. Editing a rail is detected and rejected; if a rail seems wrong, end with TICKET-BLOCKED and say why.
Never delete, skip, or weaken a test to make a gate pass. Newly added test-suppression markers (skipped or expected-to-fail tests) fail review.

Quota discipline (Antigravity-specific)

Quota is per-request and weekly; waste is lockout. Read a file once and remember it; never re-read what you already saw.
Prefer the smallest possible diff. Edit files surgically; never regenerate a whole file to change three lines.
Do not spawn subagents unless your instructions say to.

Completion protocol

End builder replies with exactly TICKET-DONE (all gates green, verified by you) or TICKET-BLOCKED: <reason>. Nothing else counts as done.
State assumptions you made on ambiguous points in one short list before the final marker. Do not expand scope to cover ambiguity.

이 저장소의 다른 Skills

같은 저장소

adlc

voodootikigod/adlc

Routes agentic development work to the right Agentic Development Lifecycle (ADLC) gate. Use when shaping a spec or ticket, deciding how to fan out work to models, protecting frozen rails during a build, prosecuting a change before merge, or distilling repeated review findings into defenses. Triggers on "shape this spec", "is this ticket ready", "freeze these tests", "prosecute this change", "is this safe to merge", "ADLC", "which gate", "spec-lint", "premortem", "coldstart", "rails-guard", "hollow-test", "behavior-diff".

2026-07-2812

adlc-prosecute

voodootikigod/adlc

Prosecute a change before merge (ADLC P5) — prove the tests are load-bearing rather than hollow, make behavior change visible, measure whether review would actually catch a planted defect, and record revision-bound evidence. Use before merging, or on requests like "prosecute this change", "is this safe to merge", "are these tests real", "will review catch anything".

2026-07-2812

adlc-init

voodootikigod/adlc

Bootstrap the ADLC runtime in a repository — install the gate toolkit, create the .adlc/ workspace, and wire the CI rails-guard control. Use when adopting the Agentic Development Lifecycle in a repo for the first time, when `adlc --version` fails, when `.adlc/` is missing, or on requests like "set up ADLC here", "install ADLC", "initialize the lifecycle".

Refute-charter review discipline for prosecuting a diff against its ticket. Use when asked to act as a prosecutor, reviewer, or to find reasons a change must not merge.

2026-07-2412

adlc-distill

voodootikigod/adlc

Run ADLC P7 distillation and maintenance workflows in Codex, including lesson-foundry, rejection-mining, skill-mining, scheduled maintenance, skill-rot, model-ratchet, review-calibration, and gate-fuzzing.

2026-07-2412

name	adlc-doctrine
description	Core operating rules for agents working inside an ADLC-orchestrated run (Antigravity Booster). Use whenever executing a ticket, reviewing a diff, or acting as part of an agb fleet. Encodes quota discipline, evidence rules, and scope discipline.

ADLC Doctrine (fleet operating rules)

Evidence or it didn't happen

"I fixed it" is a claim. A command you ran whose output you quote is evidence. Never state a result you did not verify by execution.
If a gate command is named in your instructions, run it yourself before declaring success.

Scope discipline

Touch only files inside your declared scope. An out-of-scope edit fails the whole ticket mechanically — there is no partial credit.
Rails (test files, contracts, CI config named as read-only) are frozen. Editing a rail is detected and rejected; if a rail seems wrong, end with TICKET-BLOCKED and say why.
Never delete, skip, or weaken a test to make a gate pass. Newly added test-suppression markers (skipped or expected-to-fail tests) fail review.

Quota discipline (Antigravity-specific)

Quota is per-request and weekly; waste is lockout. Read a file once and remember it; never re-read what you already saw.
Prefer the smallest possible diff. Edit files surgically; never regenerate a whole file to change three lines.
Do not spawn subagents unless your instructions say to.

Completion protocol

End builder replies with exactly TICKET-DONE (all gates green, verified by you) or TICKET-BLOCKED: <reason>. Nothing else counts as done.
State assumptions you made on ambiguous points in one short list before the final marker. Do not expand scope to cover ambiguity.