[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FF4Q0XX5P8SWG2ZR8BD1AP":3,"skill-same:01M7FF4Q0XX5P8SWG2ZR8BD1AP":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7FF4Q0XX5P8SWG2ZR8BD1AP","to-questionnaire",null,"Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","heynemann\u002Fdotfiles-stow","heynemann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60965?v=4","01M7DFBD9ZDB2J2QE7R4AR0PES","Bernardo Heynemann","01M7FERV0J6GMQ0RHEH6EHGYRW",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fmunder\u002Fskills-sh\u002F.agents\u002Fskills\u002Fto-questionnaire\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: to-questionnaire\ndescription: Turn a decision you can't fully answer into a questionnaire for someone else to fill in.\ndisable-model-invocation: true\n---\n\nTurn 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 over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.\n\n**Grill the send, not the subject.** Interview the user only about the _send_, which they can always answer: who it goes to, and what they need back. The questions in the document then target the **gap** between what the recipient knows and what the user needs.\n\n\n1. **Who is it going to?** Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.\n\n2. **What do you need back?** Ask, in one exchange, the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.\n\n3. **Write the questionnaire.** Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to `to-questionnaire-\u003Cslug>.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.\n\n## Document structure\n\nFrame the document as a **discovery questionnaire**: the user lacks context, the recipient holds it. Order questions most-important-first, since async means you may only get one pass, and group them under `##` headings by theme once there are more than a handful. Write it using the template below.\n\n\u003Cquestionnaire-template>\n\n# \u003CQuestionnaire title>\n\n**Purpose:** why this questionnaire exists and the decision riding on it.\n\n**From:** \u003Cthe user>, **To:** \u003Cthe recipient>, **How your answers will be used:** \u003Cwhere they go>\n\n## Context\n\nOne paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.\n\n## How to answer\n\nDeadline and rough effort. Partial answers and \"I don't know\" are useful: flag anything you're unsure of rather than skipping it.\n\n## \u003CTheme heading>\n\nOne `##` section per theme. Under each, its questions, most-important-first. Every question is one idea, never compound, with an answer stub directly beneath, and a one-line _why this matters_ only where the question could be misread or invite a throwaway answer.\n\n\u003Cquestion-example>\n### What load is the system expected to handle at launch?\n\n_Why this matters: it decides whether we provision for burst traffic now or defer it._\n\n>\n\u003C\u002Fquestion-example>\n\n## Anything else?\n\nA closing catch-all: anything we didn't ask that we should know?\n\n\u003C\u002Fquestionnaire-template>\n","Turn 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 over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.\n\n**Grill the send, not the subject.** Interview the user only about the _send_, which they can always answer: who it goes to, and what they need back. The questions in the document then target the **gap** between what the recipient knows and what the user needs.\n\n\n1. **Who is it going to?** Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.\n\n2. **What do you need back?** Ask, in one exchange, the specific decisions or facts the user can't resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.\n\n3. **Write the questionnaire.** Draft questions aimed at the gap from steps 1–2, following the Document structure below. Write it to `to-questionnaire-\u003Cslug>.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.\n\n## Document structure\n\nFrame the document as a **discovery questionnaire**: the user lacks context, the recipient holds it. Order questions most-important-first, since async means you may only get one pass, and group them under `##` headings by theme once there are more than a handful. Write it using the template below.\n\n\u003Cquestionnaire-template>\n\n# \u003CQuestionnaire title>\n\n**Purpose:** why this questionnaire exists and the decision riding on it.\n\n**From:** \u003Cthe user>, **To:** \u003Cthe recipient>, **How your answers will be used:** \u003Cwhere they go>\n\n## Context\n\nOne paragraph orienting a recipient who wasn't in the user's head. Enough to answer well, not a page.\n\n## How to answer\n\nDeadline and rough effort. Partial answers and \"I don't know\" are useful: flag anything you're unsure of rather than skipping it.\n\n## \u003CTheme heading>\n\nOne `##` section per theme. Under each, its questions, most-important-first. Every question is one idea, never compound, with an answer stub directly beneath, and a one-line _why this matters_ only where the question could be misread or invite a throwaway answer.\n\n\u003Cquestion-example>\n### What load is the system expected to handle at launch?\n\n_Why this matters: it decides whether we provision for burst traffic now or defer it._\n\n>\n\u003C\u002Fquestion-example>\n\n## Anything else?\n\nA closing catch-all: anything we didn't ask that we should know?\n\n\u003C\u002Fquestionnaire-template>\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","e4d0a0940fd53fc8a3a1e1dcb967c0a18ea8ba0f","omp\u002F.omp\u002Fprofiles\u002Fmunder\u002Fskills-sh\u002F.agents\u002Fskills\u002Fto-questionnaire","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow","https:\u002F\u002Fgithub.com\u002Fheynemann","http:\u002F\u002Fwww.thumbor.org","CTO @ Flutter Brazil | Former Meta & Coinbase","2026-10-29 20:46:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add heynemann\u002Fdotfiles-stow --skill to-questionnaire",{"tool":39,"command":40},"bunx","bunx skills add heynemann\u002Fdotfiles-stow --skill to-questionnaire",{"tool":42,"command":43},"pnpm","pnpm dlx skills add heynemann\u002Fdotfiles-stow --skill to-questionnaire","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fmunder\u002Fskills-sh\u002F.agents\u002Fskills\u002Fto-questionnaire\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",166,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fmunder\u002Fskills-sh\u002F.agents\u002Fskills\u002Fto-questionnaire\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FFA0PAN04C2DVK6A7CXK6K","unity-scriptableobjects","Architect Unity 6.3 LTS data and decoupling with ScriptableObjects: config\u002Fdata assets, shared runtime variables, event channels, and runtime sets\u002Fregistries. Use when designing data-driven systems, replacing singletons\u002Fmanagers, creating .asset data with CreateAssetMenu, or when the user mentions ScriptableObject, SO architecture, or data assets.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-scriptableobjects\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7FF9SPKA8BC4EGCHJGGJK5P","unity-package-management","Adds, removes, upgrades, and discovers Unity (UPM) packages from outside the Editor. Use for headless or CI package installs, verifying package IDs and versions, or choosing which packages a game needs. The Unity CLI doesn't manage packages.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-package-management\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FF9KBCKR352R6ZSY2BB2J3","unity-input-system","Wire player input in Unity 6.3 LTS with the Input System package: Input Actions, action maps, the PlayerInput component, and reading values via callbacks or polling. Use when the project has a .inputactions asset or com.unity.inputsystem, or when the user mentions the Unity Input System, InputAction, action maps, PlayerInput, control schemes, or rebinding.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-input-system\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FF9FREKNGB4PQP8ZHTN1D8","unity-ecs-patterns","Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-ecs-patterns\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FF99B1DV7RDAY98QVFFMA9","unity-csharp-scripting","Write Unity 6.3 LTS C# gameplay scripts: the MonoBehaviour lifecycle (Awake\u002FOnEnable\u002FStart\u002FUpdate\u002FFixedUpdate\u002FLateUpdate), GameObject and component access, coroutines, and Inspector serialization. Use when creating or editing .cs scripts in a Unity project, or when the user mentions MonoBehaviour, Start\u002FUpdate, GetComponent, SerializeField, coroutines, or \"Unity script\".","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-csharp-scripting\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7FF8ZK7PAPR4QZ44SY9ZDAJ","unity-cli","Controls the Unity Editor and projects from the command line, driving a running Editor to edit scenes and assets or run C#. Use when asked to install or manage Editors, licenses, or projects, set up version control, build, test, configure the Unity MCP server, or run any unity command.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-cli\u002FSKILL.md",[],[]]