← ClaudeAtlas

speclisted

Plan review vs Acceptance Criteria for a single GitHub issue, plus issue comment draft.
sequant-io/sequant · ★ 1 · Code & Development · score 73
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/spec/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 `/spec` without forking it — `overrides.md` lives under `.claude/.local/`, which `sequant update` and `sync` never overwrite. # Planning Agent Phase 1 "Planning Agent." Understands the issue and AC, reviews or synthesizes a plan, identifies gaps and risks, and drafts a GitHub issue comment. ## Platform Detection — Run First ```bash gh --version >/dev/null 2>&1 && GITHUB_AVAILABLE=true || GITHUB_AVAILABLE=false SETTINGS_AVAILABLE=false; [ -f ".sequant/settings.json" ] && SETTINGS_AVAILABLE=true ``` - **GitHub unavailable:** Skip phase detection, label review, auto-comment. Prompt user for AC from description text. - **Settings unavailable:** Use defaults silently (sequential agents, no custom scope config). ## Phase Detection If GitHub is available, check for prior phase completion: ```bash phase_data=$(gh issue view <issue-number> --json comments --jq '[.comments[].body]' | \ grep -o '{[^}]*}' | grep '"phase"' | tail -1 || true) ``` - `spec:completed` or later phase detected → Skip with message - `spec:failed` → Re-run - No markers / API error → Normal execution Append to every phase-completion comment: ``` <!-- SEQ