plan-tune

You can reduce repetitive AskUserQuestion prompts by applying per-question preferences such as never-ask or always-ask. This aligns prompt activation with your observed behavior to reduce noise and improve outcomes.

Per-question tuning is the process of adjusting which AskUserQuestion prompts fire across gstack skills by analyzing declared preferences versus observed behavior. It controls activation at per-skill and per-project levels.

Yes, you can enable proactive prompts by analyzing a dual-track developer profile that compares what you declare against what your behavior suggests. This surfaces new prompts aligned with developer psychographics when patterns indicate repetitive prompts.

Yes, plan-tune integrates with the gstack environment and supports Bash, Read, Write, Edit, Glob, Grep, and AskUserQuestion to control prompt activation at per-skill and per-project levels.

The best way to stop unnecessary prompts is to run a tuning evaluation that inspects your dual-track profile and applies per-question preferences like ask-only-for-one-way. This disables repetitive prompts across skills and projects.

You should avoid per-question prompt tuning when you need every prompt to fire regardless of user behavior, or if your project lacks an established gstack environment with Bash, Read, Write, and Edit integration for controlling activation.