[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78GYYTPF0Z3SY412PCND261":3,"skill-same:01M78GYYTPF0Z3SY412PCND261":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M78GYYTPF0Z3SY412PCND261","to-questionnaire",null,"Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","sergehas\u002Fganttee","sergehas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F55877559?v=4","01M78GWP103XC9MZP2826NNTF3","01M78GWP22QVFBQNG8FAPPHE7Z",1,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fto-questionnaire\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: to-questionnaire\ndescription:\n  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\nto one person to fill in async, or fill out together over a meeting. The recipient holds knowledge\nthe 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\nanswer: who it goes to, and what they need back. The questions in the document then target the\n**gap** between what the recipient knows and what the user needs.\n\n1. **Who is it going to?** Ask, in one exchange, the recipient's role, expertise, and relationship\n   to the user. This fixes the questionnaire's tone and how much context it must carry. Done when\n   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\n   resolve alone and needs from this person. Done when you have a concrete list of what the user\n   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\n   Document structure below. Write it to `to-questionnaire-\u003Cslug>.md` in the current directory (slug\n   from the topic) and report the path. Done when the file exists and every item the user named in\n   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.\nOrder questions most-important-first, since async means you may only get one pass, and group them\nunder `##` 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\npage.\n\n## How to answer\n\nDeadline and rough effort. Partial answers and \"I don't know\" are useful: flag anything you're\nunsure 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\nidea, never compound, with an answer stub directly beneath, and a one-line _why this matters_ only\nwhere 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\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\nto one person to fill in async, or fill out together over a meeting. The recipient holds knowledge\nthe 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\nanswer: who it goes to, and what they need back. The questions in the document then target the\n**gap** between what the recipient knows and what the user needs.\n\n1. **Who is it going to?** Ask, in one exchange, the recipient's role, expertise, and relationship\n   to the user. This fixes the questionnaire's tone and how much context it must carry. Done when\n   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\n   resolve alone and needs from this person. Done when you have a concrete list of what the user\n   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\n   Document structure below. Write it to `to-questionnaire-\u003Cslug>.md` in the current directory (slug\n   from the topic) and report the path. Done when the file exists and every item the user named in\n   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.\nOrder questions most-important-first, since async means you may only get one pass, and group them\nunder `##` 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\npage.\n\n## How to answer\n\nDeadline and rough effort. Partial answers and \"I don't know\" are useful: flag anything you're\nunsure 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\nidea, never compound, with an answer stub directly beneath, and a one-line _why this matters_ only\nwhere 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\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":23},true,"develop","3656175f11e1e311838b52d29a39d3173c74e3d8",".github\u002Fskills\u002Fto-questionnaire",0,"https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee","https:\u002F\u002Fgithub.com\u002Fsergehas","2026-11-08 07:43:24",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sergehas\u002Fganttee --skill to-questionnaire",{"tool":37,"command":38},"bunx","bunx skills add sergehas\u002Fganttee --skill to-questionnaire",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sergehas\u002Fganttee --skill to-questionnaire","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fto-questionnaire\u002FSKILL.md",[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M78GZ7BMMQP5DJ1AQ6355P0K","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M78GZ5SJJ8G7SB4VPERDM1B7","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M78GZ16YCV8G87V26BVTJZ2H","ux-css-layout","VS Code (and so Ganttee) CSS conventions, file organization, class naming, standard sizes, scrollable content, responsive layout, and text overflow\u002Fellipsis patterns. Use when writing CSS, building layouts, or fixing text truncation issues.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fux-css-layout\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M78GYVE71DN5EZ5ZFWTGFHZ2","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M78GYQFC5GFHC544FYDZBVYV","spec-router","Detect which spec-lifecycle agent a request needs (drafting, reviewing, implementing, or test planning a feature spec) and suggest the handoff — never acts without confirmation. Use whenever a message mentions a spec\u002Ffeature-spec file, a roadmap status, or spec review\u002Fimplementation\u002F draft\u002Ftest-plan intent, even without an explicit @agent mention.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fspec-router\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M78GYMM6QVMVC505BNVTB1WB","setup-skills","Configure this repo for the engineering skills: set up its issue tracker and domain doc layout. Run once before first use of the other engineering skills.","https:\u002F\u002Fgithub.com\u002Fsergehas\u002Fganttee\u002Fblob\u002Fdevelop\u002F.github\u002Fskills\u002Fsetup-skills\u002FSKILL.md",[],[]]