[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KX43NE1NB0Y2HECY515730":3,"skill-same:01M6KX43NE1NB0Y2HECY515730":65},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6KX43NE1NB0Y2HECY515730","to-questionnaire",null,"Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.","dougborg\u002Fharness-kit","dougborg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1261222?v=4","01M6KWS4PB51EYD4ZDJJSGNGB2","Doug Borg","01M6KWS4T8ZZW6SX5QZS9B5BN2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fto-questionnaire\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"to questionnaire","questionnaire","decision","async","it","make","you","meeting","answer","can","for","person","2026-11-10 10:12:30",false,"---\nname: to-questionnaire\ndescription: >-\n  Turn a decision you can't make alone into a questionnaire for the one person\n  who can answer it, filled in async or together in a meeting.\n---\n\n# To Questionnaire\n\nTurn something the user can't answer alone into a Markdown **questionnaire**\nfor one recipient who holds the missing knowledge. **Grill the send, not the\nsubject:** interview the user only about who it is for and what they need\nback, which they can always answer. Ask the way the `grilling` skill does\n(`AskUserQuestion` on Claude Code, plain text elsewhere). The questions in the document then aim at the **gap** between\nwhat the recipient knows and what the user needs.\n\n## 1. Who is it for?\n\nAsk for the recipient's role, expertise, and relationship to the user, in one\nexchange. Done when you know who they are and what they know that the user\ndoesn't; that fixes the tone and how much context the document must carry.\n\n## 2. What do you need back?\n\nAsk, in one exchange, for the specific decisions or facts the user can't\nsettle alone. Done when\nyou have a concrete list of what the user must be able to decide or do once\nthe answers come back.\n\n## 3. Write it\n\nWrite `to-questionnaire-\u003Ctopic-slug>.md` in the current directory with the\ntemplate below and report its path. Done when the file exists and every item\nfrom step 2 is covered by a question.\n\nOrder questions most important first, since an async recipient may give you\none pass, and group them under themed headings once there are more than a\nhandful. Each question asks one thing, with an answer stub beneath it. Add a\none-line reason only where the question could be misread or invite a\nthrowaway answer.\n\n```md\n# \u003CTitle>\n\n**Purpose:** why this exists and the decision riding on it.\n**From:** \u003Cuser> · **To:** \u003Crecipient> · **Answers will be used for:** \u003Cwhere they go>\n\n## Context\n\nOne paragraph for someone who wasn't in the user's head: enough to answer\nwell, not a page.\n\n## How to answer\n\nDeadline and rough effort. Partial answers and \"I don't know\" are useful;\nflag what you're unsure of rather than skipping it.\n\n## \u003CTheme>\n\n### What load must the system handle at launch?\n\n_Why this matters: it decides whether we provision for bursts now or later._\n\n>\n\n## Anything else?\n\nAnything we didn't ask that we should know?\n```\n","# To Questionnaire\n\nTurn something the user can't answer alone into a Markdown **questionnaire**\nfor one recipient who holds the missing knowledge. **Grill the send, not the\nsubject:** interview the user only about who it is for and what they need\nback, which they can always answer. Ask the way the `grilling` skill does\n(`AskUserQuestion` on Claude Code, plain text elsewhere). The questions in the document then aim at the **gap** between\nwhat the recipient knows and what the user needs.\n\n## 1. Who is it for?\n\nAsk for the recipient's role, expertise, and relationship to the user, in one\nexchange. Done when you know who they are and what they know that the user\ndoesn't; that fixes the tone and how much context the document must carry.\n\n## 2. What do you need back?\n\nAsk, in one exchange, for the specific decisions or facts the user can't\nsettle alone. Done when\nyou have a concrete list of what the user must be able to decide or do once\nthe answers come back.\n\n## 3. Write it\n\nWrite `to-questionnaire-\u003Ctopic-slug>.md` in the current directory with the\ntemplate below and report its path. Done when the file exists and every item\nfrom step 2 is covered by a question.\n\nOrder questions most important first, since an async recipient may give you\none pass, and group them under themed headings once there are more than a\nhandful. Each question asks one thing, with an answer stub beneath it. Add a\none-line reason only where the question could be misread or invite a\nthrowaway answer.\n\n```md\n# \u003CTitle>\n\n**Purpose:** why this exists and the decision riding on it.\n**From:** \u003Cuser> · **To:** \u003Crecipient> · **Answers will be used for:** \u003Cwhere they go>\n\n## Context\n\nOne paragraph for someone who wasn't in the user's head: enough to answer\nwell, not a page.\n\n## How to answer\n\nDeadline and rough effort. Partial answers and \"I don't know\" are useful;\nflag what you're unsure of rather than skipping it.\n\n## \u003CTheme>\n\n### What load must the system handle at launch?\n\n_Why this matters: it decides whether we provision for bursts now or later._\n\n>\n\n## Anything else?\n\nAnything we didn't ask that we should know?\n```\n",{"name":5,"description":7},"main","023b01bfb4a86fbf1e38a749f1044cce3e5da67d","skills\u002Fthinking\u002Fto-questionnaire",1,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit","https:\u002F\u002Fgithub.com\u002Fdougborg","http:\u002F\u002Fdougborg.org","Platforms and Infrastructure Software Engineer","2026-10-19 05:43:53",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add dougborg\u002Fharness-kit --skill to-questionnaire",{"tool":51,"command":52},"bunx","bunx skills add dougborg\u002Fharness-kit --skill to-questionnaire",{"tool":54,"command":55},"pnpm","pnpm dlx skills add dougborg\u002Fharness-kit --skill to-questionnaire","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fto-questionnaire\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",176,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fto-questionnaire\u002Fagents\u002Fopenai.yaml",[66,84,105,137,161,177],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":31},"01M6KX4J65S5FZKMSN5DQNPSZM","teach","Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fteach\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[68,78,25,79,80,81,82,83],"lessons","with","learned","record","references","sessions",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":95,"publishedAt":31},"01M6KX4FSSG7MHF00JDT5QT0BQ","svg-logo-designer","Generate SVG logos with multiple concepts, layouts, and color variations.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fsvg-logo-designer\u002FSKILL.md",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[96,97,98,99,100,101,79,102,103,104],"logo","designer","svg logo designer","SVG","color","concepts","write","read","generate",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":117,"publishedAt":31},"01M6KX4BD3J9MZPPSH4MENH7FP","documentation-writer","Writes and revises human-facing documentation — READMEs, contributor and setup guides, reference pages, architecture notes, CLAUDE.md, and changelog entries. Covers picking the right document type for the question being asked, structuring for skimming, writing examples that actually run, and keeping docs from going stale. Use when creating or rewriting docs, when a README has drifted from the code, or when deciding where a piece of information belongs. For SKILL.md and agent files, use \u002Fskill-writer instead.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[111,114],{"categoryNo":112,"categoryName":113,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":115,"categoryName":116,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000036","内容创作者",[118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,29,134,135,136],"writer","documentation writer","documentation","use","question","files","document","README","changelog","examples","type","code","notes","architecture","writing","entries","information","guides","pages",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":143,"publishedAt":31},"01M6KX47ZJ4ZWHDN3MY8SYAWZZ","adhd-mode","Shapes every response for a reader with ADHD: the next action first, numbered steps, progress restated each turn, tangents held back, concrete time estimates, wins made visible. Stays on for the rest of the session until the reader says \"stop adhd mode\". On Claude Code, the harness-kit:adhd output style does the same without invoking this skill.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fadhd-mode\u002FSKILL.md",[],[144,145,146,29,147,148,149,79,150,151,152,153,154,155,156,157,158,159,160,129],"adhd","adhd mode","mode","action","output","REST","style","progress","time","next","back","stop","session","reader","first","kit","harness",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":31},"01M6KX463Z6E18EPDW873GDHKB","wait-what","That last message didn't land: re-explain it with the missing context.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fwait-what\u002FSKILL.md",[],[168,169,170,171,172,173,79,23,174,175,176],"wait what","wait","land","explain","last","re","missing","message","context",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":186,"publishedAt":31},"01M6KX409ND71TZNSGS5QMKX3F","research","Investigates a question against primary sources (official docs, source code, specs, first-party APIs) and writes the findings, with a citation for every claim, to a Markdown file. Use when the user wants a topic researched or facts gathered from documentation, when a decision waits on facts from outside the repo, and when reading legwork should run while other work continues.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fresearch\u002FSKILL.md",[183],{"categoryNo":184,"categoryName":185,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000021","资料检索与研究",[179,187,188,29,189,190,79,191,192,121,122,193,21,194,158,195,129,196,120,197],"repo","party","facts","reading","sources","claim","work","markdown","file","run","official"]