vac-optimizer/.agents/skills/luna-verified-implement/SKILL.md

name, description

name	description
luna-verified-implement	Implement a spec or ticket with gpt-6-luna implementation subagents and independently verify the final change with the orchestrator's model and reasoning effort. Use when the user asks to implement, build, or fix work and wants delegated implementation with a verification pass.

Luna Verified Implement

Invoke $implement and follow it as the baseline workflow. Treat this skill as its delegated, verified variant.

Workflow

1. Read the spec or ticket, repository guidance, affected flow, and existing worktree changes. Record the starting commit and task-owned scope; preserve unrelated changes.
2. Split only genuinely independent, bounded work. If the change is small or one seam owns it, use one implementation agent; do not manufacture parallelism.
3. Spawn each implementation agent with fork_turns: "none", model: "gpt-6-luna", and reasoning_effort: "max". Give each its exact owned files/seam, acceptance criteria, required checks, and task-local context. Tell agents not to overwrite or revert other agents' work.
4. Wait for agents, inspect their diffs, resolve overlaps minimally, and run the implementation checks required by $implement: targeted tests and typecheck during work, then the full relevant suite once.
5. Spawn a fresh, read-only verification agent with fork_turns: "none", model and reasoning_effort set to the orchestrator's current values. Do not hard-code a different model or reasoning effort for verification. Give it the original request, current diff, and test output, but not implementation conclusions. Ask it to check correctness, regressions, specification coverage, and test evidence. Have it report findings without changing files.
6. Fix confirmed findings, rerun affected checks, and repeat verification once if fixes were needed. Run $code-review on the current working result (including staged, unstaged, and new files), passing the original spec, starting commit, and task-owned scope. Follow $implement's commit boundary: commit only when requested, otherwise hand off the verified diff.

Delegation rules

• Keep all agents in the same workspace; assign non-overlapping ownership before they edit.
• Use at most the available concurrency slots. Reserve one slot for coordination and verification.
• Do not delegate secrets, production writes, destructive operations, or changes requiring new user authority.
• If subagents are unavailable, implement directly, run the same checks, and state that delegated verification was unavailable.