Skip to content

fix(plan): drop the docs prompt #239

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kixelated merged 3 commits into from
Oct 28, 2026
Merged

fix(plan): drop the docs prompt #239

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
de83251
fix(plan): drop the docs prompt
kixelated Oct 27, 2026
315d199
Merge origin/main into plan-drop-docs-prompt
kixelated Oct 28, 2026
da01b08
Merge origin/main into plan-drop-docs-prompt
kixelated Oct 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion assets/skills/plan.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading