[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EF1S6M2Y11XKAJ0WBTMAH1":3,"skill-same:01M7EF1S6M2Y11XKAJ0WBTMAH1":51},{"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":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":44},"01M7EF1S6M2Y11XKAJ0WBTMAH1","to-questionnaire",null,"Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","vladborsh\u002Fcityplanner","vladborsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11244920?v=4","01M7EF0R90THK54J298DMGSY6D","Vlad Borsh","01M7EF0R9JWXP5WTYFG0XADXVZ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fto-questionnaire\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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,"master","25fc666e7380e9f3db2eecaba93538cf788db974","agents\u002Fclaude-skills\u002Fto-questionnaire","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner","https:\u002F\u002Fgithub.com\u002Fvladborsh","turn ideas into software applications","2026-10-30 17:49:55",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":24},[34,37,40],{"tool":35,"command":36},"npx","npx skills add vladborsh\u002Fcityplanner --skill to-questionnaire",{"tool":38,"command":39},"bunx","bunx skills add vladborsh\u002Fcityplanner --skill to-questionnaire",{"tool":41,"command":42},"pnpm","pnpm dlx skills add vladborsh\u002Fcityplanner --skill to-questionnaire","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fto-questionnaire\u002FSKILL.md",[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",166,"https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fto-questionnaire\u002Fagents\u002Fopenai.yaml",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M7EF1V091775NVRCXB0V8J7A","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7EF1K3JY985JR0SNTSSV6SB","orchestration","Use Orca orchestration for structured multi-agent coordination: threaded messages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation waits, task DAGs, decision gates, coordinator loops, or decomposing work across agents. Use `orca-cli` instead for full ownership handoffs, including requests phrased as \"hand off\", \"handoff\", \"handover\", \"give this to another agent\", or \"another worktree\" when the user did not explicitly ask to supervise, monitor, wait for results, or coordinate a DAG. Use `orca-cli` for ordinary terminal control, lightweight terminal prompts, shell commands, Orca worktree management, reading or waiting on terminals, and automation of the browser embedded inside Orca. Use Computer Use for browser windows, webviews, Orca app UI, or desktop UI outside Orca's embedded browser.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Forchestration\u002FSKILL.md",[],[],{"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":72,"publishedAt":19},"01M7EF1D1XD6AXY0Z4G9G87SJH","orca-cli","Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and the browser embedded inside the Orca app. Use when the user says \"$orca-cli\", \"use orca cli\", \"Orca worktree\", \"child worktree\", \"cardStatus\", \"spawn codex\u002Fclaude in a worktree\", \"read\u002Fwait\u002Fsend Orca terminal\", \"terminal send\", \"full handoff\", \"handover\", \"give this to another agent\", \"another worktree\", \"Orca browser\", \"orca artifacts\", \"share HTML\u002FMarkdown\", \"public artifact link\", \"share skills\", or \"control the browser inside Orca\". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Orca-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Orca's embedded browser.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Forca-cli\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7EF1BAWXJG8QP95MH9RPKZ8","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7EF18D2T2RW1QG30JWCTZYV","grill-with-docs","A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fgrill-with-docs\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7EF179QETSAQ8QZ2R4J880S","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fgrill-me\u002FSKILL.md",[],[]]