qstack-ask-plan-open-questionslisted
Install: claude install-skill hani-q/qstack
# /qstack-ask-plan-open-questions
Turn a plan's unresolved choices into explicit decisions the next reader can
trust. Ask only questions whose answers change what gets built or how it can be
executed.
## Resolve the plan
1. Use the supplied path when present.
2. Otherwise use a plan clearly referenced in the conversation.
3. Otherwise inspect `qstack/compound_engineering/plans/*/plan.html`, followed
by legacy `compound-engineering/plans/*/plan.html` and `plan.md` files. Use
the only plausible candidate; ask when more than one is plausible or none is.
Never select `.template/`.
Accept `.html` and `.md` files only. Read the whole plan and the repository's
instruction files before asking anything.
Reject template, stencil, and example artifacts even when explicitly supplied,
including anything inside `.template/` and an uninstantiated
`plan-template.html`. Report that the file is not an instantiated plan and ask
for the rendered plan path. Do not reinterpret placeholder copy as a real open
question.
### Authority
- A supplied Markdown file is a working draft only. Edit it in place when no
corresponding HTML plan exists yet.
- Once a corresponding `plan.html` exists, it is authoritative. Operate on the
HTML even if the user supplied the old Markdown path, and tell them which file
was selected.
- Never synchronize answers back from HTML to Markdown. Never maintain both.
- Never regenerate or overwrite an existing authoritative HTML plan from stale
Markdown.