Delegate
Hand the grounded spec to any implementer and collect the returned diff. The implementer is external to LSA. Optionally gate the build per-increment via checkpoint-mode paired verification (`.lsa.yaml paired_verify`).From its SKILL.md
npx -y skills add NVZver/claude-marketplace --skill delegateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- skips confirmationTells the agent to proceed without asking first, 1 time: "CLEAR → the implementer proceeds to the next task with no human interrupt (no picker, no question, no wait)".
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
7.6 KB, ~1.8k tokens by cl100k_base, as published. Nobody here has run it
Trace. On load, print first:
=============== [lsa/skills/delegate/SKILL.md] [lsa] ===============
LSA Delegate
See CORE.md. The handoff boundary — LSA writes no production code.
Role
Handoff.
Goal
Get a grounded spec built by the implementer the developer already uses, and collect the result. When paired_verify: checkpoint is set, gate the build increment-by-increment via an independent verifier without ever writing code itself.
Inputs
| Input | Source |
|---|---|
The grounded spec + <flow>.feature files | verify (GROUNDED) |
| The chosen implementer (Claude Code / Cursor / Copilot / human) | user |
.lsa.yaml paired_verify (off | checkpoint | async; default off) | .lsa.yaml (per ../../knowledge/conventions.md Read protocol) |
Steps
-
Read the paired-verify mode. Read
.lsa.yaml paired_verify(per the conventions Read protocol). Absent ⇒off. Values:off|checkpoint|async; schema in../../ARCHITECTURE.md§3. Observable result: the mode is named back to the human. (→ mode) -
Package the spec +
.featurefiles as repo files — the self-contained handoff. (→ handoff) -
Branch on the mode:
-
off(default / absent) — unchanged delegation (G2). Dispatch to the developer's implementer (this runs outside LSA), then await the returned diff. Inject no pause instruction and dispatch no verifier — byte-for-byte today's behavior. The implementer is a floored routing surface (lsa:delegate— never resolves belowinherit; code quality is load-bearing) per../../knowledge/model-routing.md. Skip to Step 6. (→ delegated → diff) -
async— refuse, do not degrade (G3). ERROR:async (concurrent-interrupt model) is not yet implemented — reserved for a later pitch. Do not fall back tocheckpointoroff; do not dispatch. Stop here — no silent degradation. -
checkpoint— inject the pause+signal protocol, then gate per increment (G4–G8, G10). Continue to Step 4.
-
-
Inject the checkpoint protocol into the handoff (G4, G5, G10).
Delegate OWNS the checkpoint-signal note path. Before injecting, delegate picks one ephemeral note path (a scratchpad / gitignored location — not committed) and passes the same path to both the implementer (the writer, in this step) and
observer:verify-checkpoint(the reader, Step 5). The path locates the note; its contents are the four contract fields —target·since·spec·status— defined once in the reader contract,observer/skills/verify-checkpoint/SKILL.md:22-37§"The checkpoint-signal contract".-
Agent-dispatched implementer (delegate dispatches it via the
Agenttool): inject into the handoff prompt an instruction that, after each plan task F-K, the implementer MUST:- Write a checkpoint-signal note at the delegate-provided path, carrying exactly the four contract fields with the meanings the reader contract defines (link above) — no extra fields, none omitted.
- Stop and await conformance clearance — do not begin the next task until the verifier's verdict clears the boundary.
Observable result: the handoff prompt names the delegate-owned note path and contains the after-each-F-K write-note-then-stop instruction naming all four fields.
-
Non-agent implementer (human / Cursor / Copilot — not dispatched via the
Agenttool) (G10): state that the pause-protocol is ADVISORY — delegate cannot enforce a pause on an implementer it does not drive. Emit the same four-field note protocol as guidance, but make no claim of enforcement. Do not silently assert the boundary is gated.
-
-
Gate each signalled increment (G6, G7, G8). For each checkpoint the agent implementer signals:
- Dispatch
observer:verify-checkpointin its per-increment mode (via theAgenttool) to grade that one signalled increment (does · only, scoped to the note'starget). Pass it the same ephemeral note path delegate provided the writer in Step 4, so the reader reads the file the writer wrote — this isverify-checkpoint's first-class per-increment invocation mode (../../../observer/skills/verify-checkpoint/SKILL.md), not its standalone/loopmode. Resolve the dispatch's model tier for surface-keylsa:delegate.verify-checkpointper../../knowledge/model-routing.md— pass it as theAgentmodelparameter (absent ⇒inherit) and echo the resolved tier in the dispatch line. - Gate on the verdict (G7):
- CLEAR → the implementer proceeds to the next task with no human interrupt (no picker, no question, no wait).
- BLOCK → surface the block to the human before the next task begins (turn-final delivery, not buried in a subagent transcript —
../../../core/skills/output/SKILL.mdRule 7).
- Keep the verifier independent (G8): it runs read-only per its own contract; never fold its verdict into the implementer's authoring context — the verdict lands as a distinct artifact the implementer could not author (
../reconcile/SKILL.md:58). Delegate orchestrates the loop; it writes no code and grades nothing itself.
- Dispatch
-
Await and return the diff. Collect the implementer's returned diff, ready for
reconcile. (→ diff) -
The final reconcile still runs (G9). Checkpoint mode does not replace the final
lsa:reconcile— per-increment does·only verdicts gate the boundaries, but the whole-diff does · only · all reconcile still runs after delegation (../reconcile/SKILL.md). Observable result: delegation completing hands off toreconcileas it does inoffmode.
Output
The implementer's diff, ready for reconcile. In checkpoint mode, additionally: per-increment CLEAR/BLOCK verdicts (authored by the independent verifier, not delegate), each CLEAR auto-clearing its boundary and each BLOCK surfaced to the human before the next task.
Constraints
- LSA writes no production code — the implementer is external. Delegate orchestrates the checkpoint loop but writes no code; the implementer writes code, the verifier grades read-only.
- Only delegate a
GROUNDEDspec (CORE §6). asyncnever degrades — it errors and stops; it does not fall back tocheckpointoroff(G3).- Checkpoint does not replace reconcile — the final whole-diff
lsa:reconcilestill runs after delegation (G9). - The verifier is independent — its verdict is never folded into the implementer's authoring context (
../reconcile/SKILL.md:58) (G8). - No silent enforcement claim — for a non-agent implementer the pause-protocol is advisory only (G10).
- Delegate owns the note path — the checkpoint-signal note path is chosen by delegate and passed as the SAME ephemeral (scratchpad / gitignored, not committed) path to both the writer (implementer) and the reader (
observer:verify-checkpoint); the four fields are unchanged.
/lsa:delegate — manual invocation.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.