issues

Mark a docs/issues/ ticket as fixed after the change has shipped. Trigger when the user says "close ticket NNNN", "mark NNNN fixed", "ship issue 0010", "the invoicing bug is done", or after a successful merge of an issue branch. Sets Status to fixed with the merge commit SHA, prompts for or fills the Verification section based on what was actually tested, and moves the line in docs/issues/INDEX.md from its Open section to Done. Also handles paired tickets shipped together (each keeps its own Verification but they share the commit SHA). This is the diagnosis-preserving cousin of /plan-close — pick this one when the closed ticket should remain a useful read for the next person hitting the same bug.

Bootstrap a docs/issues/ folder in the current repo for tracking bugs, features, and incidents as one markdown file per issue. Use whenever the user wants to set up issue tracking inside a repo, asks for a "ticket folder" / "bug tracker folder" / "docs/issues directory", or before they file the first ticket. /issue-new auto-inits if missing, so /issue-init is primarily for explicit setup or for refreshing the seed README/INDEX. This is the bug-write-up cousin of /plan-init — pick this one when issues need a full diagnosis record (symptom, repro, root cause, fix, verification) and a branch-on-start workflow.

File a new ticket under docs/issues/ for a bug, feature request, incident, or open question that should be tracked but isn't being fixed right now. Trigger whenever the user says "log this as a bug", "open a ticket for X", "track this issue", "create an issue for Y", "we should remember to fix Z", or describes something worth filing — even when they don't explicitly say "ticket". Auto-initializes the docs/issues/ scaffolding if missing, picks the next NNNN, writes the file with the template pre-filled from conversation context, and updates docs/issues/INDEX.md so the board stays current. Reach for this skill instead of /plan-add when the issue needs a real diagnosis record (symptom, repro, root cause, fix, verification) rather than a quick todo line.

Begin work on an existing ticket in docs/issues/. Trigger when the user says "start ticket NNNN", "pick up issue 0016", "let's tackle the invoicing bug", "work on the Save Template thing", or otherwise indicates they're starting on something already filed. This skill enforces the project's alignment-before-implementing rule — before any code is written, the agent restates the symptom, shares a root-cause hypothesis (or names what needs read-only investigation first), proposes the minimum fix, and waits for the user to agree. Only then does it flip the ticket's Status to in-progress, create a {domain}/{kebab} branch, and move the line in docs/issues/INDEX.md to "In progress". This is the workflow-heavy cousin of /plan-update — pick this one when the work needs alignment and a dedicated branch, not just a status field flip.