Individual skill
to-questionnaire
把你无法完整回答的 decision 转成一份交给他人填写的 questionnaire。
skills/productivity/to-questionnaire/SKILL.md
Source commit 5b57718666917f8a6a0ff3066ae8d5ec386baef4
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 5,698
- Repository last updated
- Nov 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agent Repository topic
- chinese Repository topic
- developer-skills Repository topic
- productivity Repository topic
- prompt-engineering Repository topic
- skills Repository topic
- translation Repository topic
- vibe-coding Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,911 bytesagents/openai.yamlasset · 161 bytes
Read excerpt
把用户无法独自回答的事情转成一份 **questionnaire**:一份交给某个人异步填写,或在会议中一起填写的 Markdown document。Recipient 掌握用户缺少的知识;questionnaire 要把这些知识提取出来。
**Grill the send, not the subject。** 只围绕用户始终能够回答的 _send_ 进行访谈:发送给谁,以及需要对方返回什么。Document 中的问题再针对 recipient 所知与用户所需之间的 **gap**。
1. **发送给谁?** 在一次交流中询问 recipient 的 role、expertise 和与用户的关系。这会确定 questionnaire 的语气,以及需要携带多少 context。知道 recipient 是谁,以及对方掌握哪些用户不掌握的知识后,这一步完成。
2. **需要返回什么?** 在一次交流中询问用户无法独自解决、需要此人提供的具体 decisions 或 facts。当你得到一份具体清单,明确用户最终必须能做什么或决定什么时,这一步完成。
3. **编写 questionnaire。** 根据步骤 1–2 的 gap 起草问题,并遵循下面的 Document structure。把文件写到当前目录的 `to-questionnaire-<slug>.md`(slug 来自主题),然后报告路径。当文件存在,且步骤 2 中用户列出的每项内容都有问题覆盖时完成。
## 文档结构
把 document 定位为 **discovery questionnaire**:用户缺少 context,而 recipient 掌握它。按重要程度降序排列问题,异步沟通可能只有一次机会;问题超过少量时,按主题放在 `##` headings 下。使用以下 template。