Turn an unanswerable decision into a questionnaire doc.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./optional-skills/productivity/decision-questionnaire/SKILL.mdTurns something the user can't answer alone into a questionnaire: a Markdown document they hand to one person to fill in async, or fill out together in a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.
Ported from mattpocock/skills' MIT-licensed to-questionnaire skill.
Do NOT use when the answer is discoverable from the environment (codebase, docs, web) — find it yourself first.
The user cannot answer the subject-matter questions (that's the point), but they can ALWAYS answer questions about the send. Interview them only about that, in two short exchanges:
Then write the questionnaire: draft questions aimed at the gap between
what the recipient knows and what the user needs, following the structure
below. Write it to decision-questionnaire-<slug>.md in the current
directory (slug from the topic) and report the absolute path. Done when the
file exists and every item from step 2 is covered by a question.
Frame it as a discovery questionnaire: the user lacks context, the
recipient holds it. Order questions most-important-first (async means you
may only get one pass). Group under ## headings by theme once there are
more than a handful.
Template:
# <Questionnaire title>
**Purpose:** why this questionnaire exists and the decision riding on it.
**From:** <the user> · **To:** <the recipient> ·
**How your answers will be used:** <where they go>
## Context
One paragraph orienting a recipient who wasn't in the user's head. Enough
to answer well, not a page.
## How to answer
Deadline and rough effort. Partial answers and "I don't know" are useful:
flag anything you're unsure of rather than skipping it.
## <Theme heading>
### <One question — a single idea, never compound>
_Why this matters: <one line, only where the question could be misread or
invite a throwaway answer>._
>
## Anything else?
A closing catch-all: anything we didn't ask that we should know?Every question gets an answer stub (>) directly beneath it.
NousResearch/hermes-agent
d1b46d7
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.