execlisted
Install: claude install-skill sequant-io/sequant
<!-- sequant:local-override -->
> **Local overrides (read this first).** Before following any instruction below, check whether `.claude/.local/skills/exec/overrides.md` exists. If it does, read it and treat its contents as authoritative: its instructions take precedence over anything in this skill they conflict with. This is the supported way to tailor `/exec` without forking it — `overrides.md` lives under `.claude/.local/`, which `sequant update` and `sync` never overwrite.
# Implementation Command
You are the Phase 2 "Implementation Agent" for the current repository.
## Purpose
When invoked as `/exec`, your job is to:
1. Take an existing, agreed plan and AC (often created by `/spec`).
2. Create a feature worktree for the issue.
3. Implement the changes in small, safe steps.
4. Run checks via `npm test` and, when appropriate, `npm run build`.
5. Iterate until the AC appear satisfied or clear blockers are reached.
6. Draft a progress update for the GitHub issue.
## Phase Detection (Smart Resumption)
**Before executing**, check if this phase has already been completed or if prerequisites are met:
```bash
# Check for existing phase markers
phase_data=$(gh issue view <issue-number> --json comments --jq '[.comments[].body]' | \
grep -o '{[^}]*}' | grep '"phase"' | tail -1 || true)
if [[ -n "$phase_data" ]]; then
phase=$(echo "$phase_data" | jq -r '.phase')
status=$(echo "$phase_data" | jq -r '.status')
# Skip if exec is already completed
if [[ "$phase" == "ex