issue

Kit Preamble — issue

Kit Script Root

Kit root: ${CLAUDE_PLUGIN_ROOT}

• Absolute path above → plugin install (substituted at load time; no project scripts/ dir): prefix every kit script command with it, e.g. bash <kit-root>/scripts/checkpoint.sh …. Absolute paths also work from worktrees.
• Literal ${…} placeholder above → standalone layout: run commands as written.

Project Context Detection

Run these checks silently at the start. Use results to adapt behavior:

• [ -f issues.md ] — if true, this project uses the sprint system. Respect issue numbering and STATUS.md.
• [ -f docs/sprint_state.md ] — if true and Status shows running, a sprint is active. Be aware of parallel work in worktrees.
• [ -f docs/prd_digest.md ] — if true, read it for quick project context before starting.

Kit Rules

• Verify gh auth status before any GitHub operation.

Algorithm

Phase 1 — Context Gathering

1. Read $ARGUMENTS. If empty, ask the user for a description and stop.
2. Read issues.md. If not found, tell the user to run /kickoff first and stop.
3. Parse the highest issue number from issues.md using ### ISSUE-(\d+): regex. Next issue number = max + 1.
4. Read the following docs in parallel (skip any that don't exist):
   • docs/prd_digest.md
   • docs/requirements.md
   • docs/ux_spec.md
   • docs/architecture.md
   • docs/data_model.md
   • docs/test_plan.md
   • docs/design_philosophy.md
   • docs/design_system.md
   • docs/wireframes.md
   • docs/interactions.md
   • docs/copy_guide.md

If none of the planning docs exist, warn the user but proceed with issues.md + STATUS.md only.

4.5) Set design context flag:

• has_design_docs = true if both docs/design_philosophy.md and docs/wireframes.md exist; false otherwise.
• This flag controls whether design doc updates are offered in Phase 2.

Phase 2 — Doc Update Detection & Scope Estimation