From 1fb4232671d30aa867e3e7b0c74d48a989e460c5 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Wed, 22 Apr 2026 08:08:59 -0500 Subject: chore: remove fix-issue skill, superseded by start-work The fix-issue skill has been replaced by start-work, which covers the same ground (picking up a ticket with a known fix and carrying it through to handoff) with a seven-phase structure and three user-approval gates. Deleted fix-issue/SKILL.md and swept the references. Updated: - Makefile SKILLS list: remove fix-issue, add start-work so make install creates the right symlink. - brainstorm/SKILL.md: implementation-path list points at start-work. - debug/SKILL.md description: both "do NOT use for ticket-driven work" and "Companion to" references updated. - review-code/SKILL.md description: "drafting implementation" redirect updated. No change in meaning. Every old fix-issue context now names start-work. --- brainstorm/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'brainstorm') diff --git a/brainstorm/SKILL.md b/brainstorm/SKILL.md index 2f84aa6..1b9ad08 100644 --- a/brainstorm/SKILL.md +++ b/brainstorm/SKILL.md @@ -155,7 +155,7 @@ After the design is written and agreed: - **Each open question** → run `arch-decide` to record as an ADR - **System-level implications** → run `arch-design` to update the architecture brief -- **Implementation** → whatever the project's implementation path is (`fix-issue`, `add-tests`, or direct work) +- **Implementation** → whatever the project's implementation path is (`start-work`, `add-tests`, or direct work) Link the design doc from wherever it's being implemented (PR description, ticket, commit). -- cgit v1.2.3