← 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. ## Worktree Contract <!-- BEGIN: spec-worktree-contract (#899) --> **No worktree needed. Planning happens in the main repository directory.** The worktree is created later — by the orchestrator (`/fullsolve` Phase 1.5, or `sequant run`) when one is driving, otherwise by `/exec` itself. This skill only ever *reads* `git worktree list`, for in-flight collision detection. **Do not create a worktree here, and do not describe one as existing after `/spec`** — downstream skills that trust such a claim end up implementing in the main checkout (#899, and the line this restores was dropped by #515). <!-- END: spec-worktree-contract (#899) --> ## 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=