From de832519289033ee070cdc3584426c7ef87d3160 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 27 Oct 2026 16:34:41 -0700 Subject: [PATCH] fix(plan): drop the docs prompt The prompt fired on nearly every plan, since almost every quest changes an API or flag, and the answer was nearly always inline only. Co-Authored-By: Claude Opus 5.5 --- assets/skills/plan.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/skills/plan.md b/assets/skills/plan.md index ed12a0f8..4a1b913d 100644 --- a/assets/skills/plan.md +++ b/assets/skills/plan.md @@ -12,7 +12,7 @@ Every follow-up the user picks goes through this interview, including edits to e A background agent that cannot prompt never creates or edits quests itself, so this skill can run in the foreground. Search other quests and epics to keep the larger plan consistent. -When the work changes what a user sees (a wire, an API, a flag, a dashboard), ask whether it needs documentation the feature quest cannot carry inline (a new page or guide), and recommend a quest for that; docs a change makes stale stay in that change. +Docs a change makes stale stay in that change. Begin the interview by scoping the goal: the observable outcome, why it matters, and its important boundaries and non-goals. Restate the goal in one sentence and get it confirmed before moving on to implementation decisions.