stay-on-target's 04-clarify/05-plan cause excessive ceremony gates and premature clarifying questions

Open
#122 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
markdown

Research direction

Read 03-prior-art.md, 04-clarify.md, 05-plan.md, and 06-verify.md, then compare their ordering and gates with the cited session-history query findings. Done means the workflow investigates before asking when possible and avoids confirmation ceremony for reversible, trivial work while preserving behavior for genuinely blocked or risky changes.

Written by the indexing model from the issue text.

Description

stay-on-target's SessionStart hook unconditionally injects "Focused Development Mode" into every session, via 04-clarify.md and 05-plan.md. Two concrete problems, backed by a 2026-06-10 query over session history (cq):

  1. Ceremony gates. The annoying tail of AskUserQuestion volume (17-87/day in one project) is not legitimate design forks, it's ceremony questions like "Ready to start?" or "Push it?" traceable directly to 05-plan/06-verify requiring a human-reviewable plan and confirmation before nearly anything.

  2. Ask-before-investigate. The genuinely bad questions (rare, about 5 across 6 weeks out of 200+ AskUserQuestion calls) share one root cause: asking before doing a cheap lookup that would have answered the question. This happens because 04-clarify's "ask one question at a time" urge fires before 03-prior-art's "explore before proposing" has a chance to run.

Expected: the plugin's clarify/plan behaviors should bias toward investigating first and asking only when genuinely blocked (missing input, a decision only the user can make), not toward gating on ceremony confirmations for reversible, low-risk actions.

Options considered:

  • Rework 04-clarify to require attempting a cheap lookup before asking a clarifying question, when one is available
  • Scope 05-plan's confirmation gate to non-trivial/risky changes only, skipping it for reversible or explicitly-requested trivial work
  • Add an escape hatch users can invoke to skip planning ceremony for a single request without disabling the plugin entirely

Related: 01-git-state and 07-drift are not implicated and should stay as-is.

Dominant language
Python
Stars
10
Forks
3
Avg merge
18h 9m
Merged PRs (30d)
18

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from technicalpickles/pickled-claude-plugins

All issues in technicalpickles/pickled-claude-plugins

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.