The generated questionnaire may persist and disclose relationships or sensitive decision context
Source references: 2The template requires the sender, recipient, intended use, decision context, and enough background for the recipient to answer. The Skill does not require a privacy, confidentiality, or recipient-authorization check before saving or handing over the document.
If the user supplies sensitive personnel, customer, business, or technical details, they may remain in a Markdown file in the current directory and be disclosed when the questionnaire is shared or when others can access that directory.
The Skill does require saving the questionnaire in the current directory and including the sender, recipient, intended use, decision context, and enough background to answer. If the user supplies personal or confidential project details, the saved file would retain them. However, this is part of the stated purpose of gathering information from a user-chosen recipient. The source neither requires sensitive data nor sends the file or exposes it to an unauthorized person, so it supports only a conditional retention risk, not improper disclosure. A user can restrict names, confidential context, and the save location.
This assessment concerns the code and conditions shown, not proof that harm has occurred.3. **Write the questionnaire.** Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to `to-questionnaire-<slug>.md` in the current directory (slug from the topic) and report the path. Done when the file exists and every item the user named in step 2 is covered by a question.Show 1 other places
**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>## ContextOne paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.