hieuphung97/dely

Setup

Write exactly one managed block into the project's AGENTS.md. Discover models and effort from the installed harnesses. Do not store a catalogue. Do not install, trust, or enumerate anything.

Read AGENTS.md first. Replace only the region between this skill's own markers. Prose outside the block is not read, merged, moved, or deleted.

Two rows only

The managed block configures deployment preferences for implement and review — nothing else. There is no coordinator or orchestrator field, because Orca is the constant, required execution plane. There is no control row, because the current interactive session already exists and is never dispatched. There is no release row, because release has no LLM worker. There is no Plan Mode field and no design-skill field: the active design method is a property of the harness and session, not a Dely setting.

Two paths

Quick. Use the current harness for both implement and review. Use that harness's defaults for model and effort, written as the literal default.

Customize. For each of implement and review, offer the discovered harnesses, models and effort levels and write what the human chooses.

Ask which path. Do not start writing until that is answered.

What to write

Exactly one block, and nothing else:

<!-- dely:begin -->
## Dely

Bounded or Architectural work invokes `dely:delivery`; Spike starts no
delivery run.

| Phase | Harness | Model | Effort |
| --- | --- | --- | --- |
| `implement` | … | … | … |
| `review` | … | … | … |
<!-- dely:end -->

If the markers already exist, replace the region between them. If they do not, append the block. Touch nothing else.

Discovery

Run these commands. They are the catalogue. Do not copy a list from this package, from memory, or from docs/.

• Claude Code models: claude -p "/model" --output-format json
• Claude Code effort: claude -p "/effort" --output-format json
• Codex: codex debug models
• Grok models: grok models
• Antigravity CLI models: agy models (offer the slug column of its TSV output)

The two Claude probes are answered locally: num_turns 0, total_cost_usd 0, no model turn. Do not treat them as a dispatch.

Codex slugs with visibility: hide are not offered. Codex reasoning levels are supported_reasoning_levels on each slug, not one vocabulary per harness.

Grok effort is not discovered by calling the model. Read the installed CLI's help and any validation already observed. Do not run a Grok prompt to learn the flag.

Antigravity CLI effort is low|medium|high, read from agy --help's --effort flag; do not prompt the model to learn it. Some model slugs already end in -high, -medium, or -low — that suffix names the model, not the effort flag, so do not strip it.

A harness that is not installed is omitted from the offer, not an error.

Kiro CLI

Kiro CLI models: kiro-cli chat --list-models --format json (offer each model_id). Kiro CLI effort is read from kiro-cli chat --help's --effort flag; do not prompt the model to learn it and do not store a catalogue. Live discovery may offer only auto — that is a valid result, not a reason to invent model names. Omit Kiro discovery that is unavailable or unusable rather than guessing.

Cursor Agent CLI

Cursor Agent CLI models: cursor-agent models (offer the slug before -). There is no --effort flag: write the literal default for Effort. Do not invent an effort vocabulary, do not strip effort suffixes from slugs, and do not synthesize parameterized [effort=…] forms. Omit Cursor discovery that is unavailable or unusable rather than guessing.

Pinning

Where a managed block exists, pin its Harness, Model and Effort for implement and review on every dispatch. The literal default in Model or Effort means the harness default is wanted: omit that flag. That is not the same as an unset cell — defaults are a deployment preference, not a reproducible pin, and the execution envelope records the configured value and, where the harness exposes it, the actual observed model and effort.

Where AGENTS.md carries no managed block, delivery runs implement and review on the current harness with harness defaults and omits the model and effort flags. Setup is a convenience over that fallback, not a precondition for it.

When a choice cannot be offered

Where a choice cannot be offered, do not make it. Take the conservative action — which may be writing a conservative value, and may be doing nothing — and report the choice that was not offered, naming what was available and how to set it; do not write that report into the managed block.

For the CLAUDE.md import: if the current harness is Claude Code, the import is absent, and setup cannot ask, write nothing and report the offer that was not made.

Refusals

Stop and report to the human, unchanged, when:

• the markers are broken (a begin without a matching end, or an end before its begin)
• more than one <!-- dely:begin --> is present
• a legacy phase table outside the block contradicts the block

Do not merge two tables, delete a legacy table, or guess which is authoritative.

Claude Code and AGENTS.md

Claude Code does not read AGENTS.md. The persistent instruction reaches Codex, Grok, Antigravity CLI, Kiro CLI, and Cursor Agent CLI natively. It reaches Claude Code only where the project has a CLAUDE.md that imports AGENTS.md.

Where the current harness is Claude Code and the project has no CLAUDE.md importing AGENTS.md, offer to create a one-line CLAUDE.md containing @AGENTS.md. The human accepts or declines. Never write it unasked.

This is not a second managed block: no markers, no configuration, a pointer at the block rather than a copy of it.

The offer is Claude-Code-only. On Codex, Antigravity CLI, and Kiro CLI the file is inert in the same sense that it is not imported. Cursor Agent CLI applies CLAUDE.md as a rule. Grok does not expand it.

What setup will not do

No plugin or skill install. No hook trust. No writes to ~/.claude, ~/.codex, ~/.grok, ~/.gemini, ~/.kiro, or ~/.cursor. No custom Kiro agent creation or modification. No coordinator installation or field. No control or release row. No enumeration or invocation of project-owned workflow plugins. No model catalogue.

Print verified install guidance only when the human explicitly asks for it.