[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KWV7SS23HQDYK4ETHVMMHE":3,"skill-same:01M6KWV7SS23HQDYK4ETHVMMHE":84},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6KWV7SS23HQDYK4ETHVMMHE","harness-issue",null,"Files a bug report, idea, or proposed change against the upstream harness repo resolved from the project's config, from any project that uses harness-kit. Two modes: open an Issue, or open a PR with a draft fix. Searches for duplicates first and shows the proposed content before filing. Use when a harness skill, agent, hook, script, or doc misbehaves or has a gap worth reporting upstream; when the user asks to file harness feedback or propose a harness fix; and when a harness retro finds an upstream-worthy item.","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\u002Fclaude-skills\u002Fharness-issue\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"harness issue","harness","issue","fix","kit","filing","project","files","bug","duplicates","log","change","write","read","gh pr","Bash","open","api","reporting","config","2026-11-10 10:12:30",false,"---\nname: harness-issue\ndescription: >-\n  Files a bug report, idea, or proposed change against the upstream harness\n  repo resolved from the project's config, from any project that uses\n  harness-kit. Two modes: open an Issue, or open a PR with a draft fix.\n  Searches for duplicates first and shows the proposed content before filing.\n  Use when a harness skill, agent, hook, script, or doc misbehaves or has a\n  gap worth reporting upstream; when the user asks to file harness feedback or\n  propose a harness fix; and when a harness retro finds an upstream-worthy\n  item.\nargument-hint: \"[issue|pr]\"\nallowed-tools: Bash(gh issue *), Bash(gh pr *), Bash(gh repo *), Bash(gh api *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(${CLAUDE_SKILL_DIR}\u002F*), Read, Edit, Write\n---\n\n# Harness Issue\n\nTurn a lesson from a downstream project into an upstream Issue (a bug, gap,\nor idea) or a Pull Request (a concrete fix) on the harness repository, without\nleaving the project. It closes the loop between the projects that consume\nharness-kit and the harness itself.\n\nIt needs `gh`, authenticated with access to the upstream repo, and a user\npresent to confirm the preview. PR mode also needs push access to the\nupstream or to a fork of it.\n\nTwo rules hold in every mode. Show the full title and body and get the user's\nconfirmation before any `gh issue create` or `gh pr create`, so nothing is\nfiled silently. Write only facts you have: when the harness-kit version,\nskill, or commit behind the finding is unknown, ask or write `(unknown)`\nrather than inventing context to look thorough.\n\n## 1. Resolve the upstream\n\n```bash\nupstream=$(${CLAUDE_SKILL_DIR}\u002Fresolve-upstream.sh)\n```\n\nThe script is the lookup the update workflow uses too: `$HARNESS_UPSTREAM`,\nthen `.claude\u002Fharness-upstream` (one line, `owner\u002Frepo`), then, in a project\nnot yet migrated to a vendored snapshot, the first source `repo` in\n`.harness-lock.json`, then its built-in default. Refer to the repo by the\nresolved name in every message to the user rather than a hardcoded\n`dougborg\u002Fharness-kit`. Done when `$upstream` holds an `owner\u002Frepo` and you\nhave told the user which repo you are filing against.\n\n## 2. Choose the mode\n\nUse `$ARGUMENTS` when it is `issue` or `pr`. Otherwise ask: \"Issue (describe a\nbug, gap, or idea) or PR (propose a concrete change)?\" Done when the mode is\nset.\n\n## 3. Gather the context\n\nFrom the conversation, pin down:\n\n- **What**: the finding in one sentence.\n- **Where**: the affected skill, agent, hook, script, or doc, with file path\n  and line when known.\n- **Why it matters**: the concrete impact (broke a workflow, surprised a user,\n  blocked a feature).\n- **Repro or suggested fix**: a minimal repro for a bug, a sketch of the fix\n  for an idea.\n\nSanitize internal paths, customer names, and secrets before they reach the\ndraft, and ask the user when you're unsure whether something is sensitive.\nDone when each of the four is filled in, asked about, or marked `(unknown)`.\n\n## 4. Search for duplicates\n\n```bash\ngh issue list -R \"$upstream\" --state all --limit 20 --search \"\u003Ckeywords>\"\ngh pr list    -R \"$upstream\" --state all --limit 20 --search \"\u003Ckeywords>\"\n```\n\nSearch by topic, not by the title you were about to write: the same work is\noften filed under a different framing (an issue saying \"the standard is\ndocumented but unenforced\" can duplicate one saying \"set up the testing\nstack\"). Try two or three phrasings of the underlying need.\n\nShow the user any related matches and ask: file new, comment on the existing\nthread, or abort. Commenting on an existing thread keeps the discussion in one\nplace: post with `gh issue comment` or `gh pr comment`, then skip to step 6.\nDone when the user has chosen, or no open or recently closed item matches.\n\n## 5a. Issue mode\n\nFirst check the finding isn't already fixed on the default branch, merged but\nnot yet released: look at the merged PRs from step 4, and search commits\npushed directly:\n\n```bash\ngh api -X GET search\u002Fcommits -f q=\"repo:$upstream \u003Ckeywords>\" --jq '.items[] | \"\\(.sha[0:7]) \\(.commit.message | split(\"\\n\")[0])\"'\n```\n\nWhen it is already fixed, tell the user and stop instead of filing.\n\nCompose a title of 70 characters or fewer and this body:\n\n```markdown\n## What\n\n\u003Cone-paragraph summary>\n\n## Where\n\n- File: `path\u002Fto\u002Faffected.md`\n- Skill \u002F agent: `\u003Cname>` (if applicable)\n- harness-kit version: `\u003Cversion from .harness\u002Flock.json>` (or `unknown`)\n\n## Why it matters\n\n\u003Cimpact>\n\n## Repro \u002F suggested fix\n\n\u003Cminimal repro or sketch>\n\n## Source context\n\nSurfaced from project `\u003Cdownstream-repo-name>` (or `unknown`) on `\u003Cdate>`.\n```\n\nShow the user the full title and body, and after they confirm:\n\n```bash\ngh issue create -R \"$upstream\" --title \"\u003Ctitle>\" --body \"$(cat \u003C\u003C'EOF'\n\u003Cbody>\nEOF\n)\"\n```\n\nDone when the issue exists and you have its URL.\n\n## 5b. PR mode\n\n1. **Name the branch**: short and descriptive, such as\n   `fix\u002Fhooks-reference-typo` or `feat\u002Fissue-template-for-retro`.\n2. **Prepare the upstream workspace**:\n\n   ```bash\n   workspace=$(${CLAUDE_SKILL_DIR}\u002Fprepare-pr-workspace.sh \"$upstream\" \"\u003Cbranch>\")\n   cd \"$workspace\"\n   ```\n\n   The script clones the upstream, or reuses a checkout under\n   `${XDG_CACHE_HOME:-~\u002F.cache}\u002Fharness-issue\u002F` (`$HARNESS_UPSTREAM_WORKSPACE`\n   overrides the root). It refuses to touch a checkout with unrelated state,\n   fast-forwards the default branch, and creates the new branch.\n\n   Without push access to the upstream, fork it now, before anything\n   pushes: run `gh repo fork --remote` in `$workspace`, so pushes go to the\n   fork. `gh pr create` then opens the PR cross-repo by default.\n3. **Check it isn't already fixed**: `git log` in the workspace. When the\n   default branch already addresses the finding (merged, just not released),\n   tell the user and stop instead of filing.\n4. **Apply the change** in `$workspace` as ordinary editing in the upstream\n   repo. Keep it minimal and focused, and link back to the downstream context\n   in the commit body rather than in code comments.\n5. **Open the PR.** From inside `$workspace`, call the Skill tool with\n   \"open-pr\", so the upstream's own validation, self-review, and CI polling\n   run against the upstream's verification command. Leave validation,\n   self-review, and CI polling to open-pr rather than running them here. Put\n   a \"Source context\" footer in the PR body, matching the Issue mode\n   template.\n\nDone when the PR exists and you have its URL.\n\n## 6. Report\n\nTell the user the upstream repo, the mode, and the URL of the issue, PR, or\ncomment. Done when all three are reported.\n\n## Several findings at once\n\nWhen a retro produces several findings, file each as its own Issue or PR so\ntriage stays clean. Batch them only when they are genuinely one concern.\n\n## Configuration\n\n- `.claude\u002Fharness-upstream`: one line, `owner\u002Frepo`. Overrides the default\n  and the old lock file.\n- `$HARNESS_UPSTREAM`: environment override for one-off runs or CI.\n- `$HARNESS_UPSTREAM_WORKSPACE`: root for cached upstream checkouts (default\n  `${XDG_CACHE_HOME:-~\u002F.cache}\u002Fharness-issue`).\n\n## Related\n\n- `\u002Fharness retro`: surfaces upstream-worthy findings during post-session\n  review and hands each one to this skill.\n- `\u002Fharness hoist`: hoists upstream files your project has already modified.\n  This skill complements it for findings that aren't yet a code diff.\n- `\u002Fopen-pr`: runs inside the upstream workspace in PR mode.\n","# Harness Issue\n\nTurn a lesson from a downstream project into an upstream Issue (a bug, gap,\nor idea) or a Pull Request (a concrete fix) on the harness repository, without\nleaving the project. It closes the loop between the projects that consume\nharness-kit and the harness itself.\n\nIt needs `gh`, authenticated with access to the upstream repo, and a user\npresent to confirm the preview. PR mode also needs push access to the\nupstream or to a fork of it.\n\nTwo rules hold in every mode. Show the full title and body and get the user's\nconfirmation before any `gh issue create` or `gh pr create`, so nothing is\nfiled silently. Write only facts you have: when the harness-kit version,\nskill, or commit behind the finding is unknown, ask or write `(unknown)`\nrather than inventing context to look thorough.\n\n## 1. Resolve the upstream\n\n```bash\nupstream=$(${CLAUDE_SKILL_DIR}\u002Fresolve-upstream.sh)\n```\n\nThe script is the lookup the update workflow uses too: `$HARNESS_UPSTREAM`,\nthen `.claude\u002Fharness-upstream` (one line, `owner\u002Frepo`), then, in a project\nnot yet migrated to a vendored snapshot, the first source `repo` in\n`.harness-lock.json`, then its built-in default. Refer to the repo by the\nresolved name in every message to the user rather than a hardcoded\n`dougborg\u002Fharness-kit`. Done when `$upstream` holds an `owner\u002Frepo` and you\nhave told the user which repo you are filing against.\n\n## 2. Choose the mode\n\nUse `$ARGUMENTS` when it is `issue` or `pr`. Otherwise ask: \"Issue (describe a\nbug, gap, or idea) or PR (propose a concrete change)?\" Done when the mode is\nset.\n\n## 3. Gather the context\n\nFrom the conversation, pin down:\n\n- **What**: the finding in one sentence.\n- **Where**: the affected skill, agent, hook, script, or doc, with file path\n  and line when known.\n- **Why it matters**: the concrete impact (broke a workflow, surprised a user,\n  blocked a feature).\n- **Repro or suggested fix**: a minimal repro for a bug, a sketch of the fix\n  for an idea.\n\nSanitize internal paths, customer names, and secrets before they reach the\ndraft, and ask the user when you're unsure whether something is sensitive.\nDone when each of the four is filled in, asked about, or marked `(unknown)`.\n\n## 4. Search for duplicates\n\n```bash\ngh issue list -R \"$upstream\" --state all --limit 20 --search \"\u003Ckeywords>\"\ngh pr list    -R \"$upstream\" --state all --limit 20 --search \"\u003Ckeywords>\"\n```\n\nSearch by topic, not by the title you were about to write: the same work is\noften filed under a different framing (an issue saying \"the standard is\ndocumented but unenforced\" can duplicate one saying \"set up the testing\nstack\"). Try two or three phrasings of the underlying need.\n\nShow the user any related matches and ask: file new, comment on the existing\nthread, or abort. Commenting on an existing thread keeps the discussion in one\nplace: post with `gh issue comment` or `gh pr comment`, then skip to step 6.\nDone when the user has chosen, or no open or recently closed item matches.\n\n## 5a. Issue mode\n\nFirst check the finding isn't already fixed on the default branch, merged but\nnot yet released: look at the merged PRs from step 4, and search commits\npushed directly:\n\n```bash\ngh api -X GET search\u002Fcommits -f q=\"repo:$upstream \u003Ckeywords>\" --jq '.items[] | \"\\(.sha[0:7]) \\(.commit.message | split(\"\\n\")[0])\"'\n```\n\nWhen it is already fixed, tell the user and stop instead of filing.\n\nCompose a title of 70 characters or fewer and this body:\n\n```markdown\n## What\n\n\u003Cone-paragraph summary>\n\n## Where\n\n- File: `path\u002Fto\u002Faffected.md`\n- Skill \u002F agent: `\u003Cname>` (if applicable)\n- harness-kit version: `\u003Cversion from .harness\u002Flock.json>` (or `unknown`)\n\n## Why it matters\n\n\u003Cimpact>\n\n## Repro \u002F suggested fix\n\n\u003Cminimal repro or sketch>\n\n## Source context\n\nSurfaced from project `\u003Cdownstream-repo-name>` (or `unknown`) on `\u003Cdate>`.\n```\n\nShow the user the full title and body, and after they confirm:\n\n```bash\ngh issue create -R \"$upstream\" --title \"\u003Ctitle>\" --body \"$(cat \u003C\u003C'EOF'\n\u003Cbody>\nEOF\n)\"\n```\n\nDone when the issue exists and you have its URL.\n\n## 5b. PR mode\n\n1. **Name the branch**: short and descriptive, such as\n   `fix\u002Fhooks-reference-typo` or `feat\u002Fissue-template-for-retro`.\n2. **Prepare the upstream workspace**:\n\n   ```bash\n   workspace=$(${CLAUDE_SKILL_DIR}\u002Fprepare-pr-workspace.sh \"$upstream\" \"\u003Cbranch>\")\n   cd \"$workspace\"\n   ```\n\n   The script clones the upstream, or reuses a checkout under\n   `${XDG_CACHE_HOME:-~\u002F.cache}\u002Fharness-issue\u002F` (`$HARNESS_UPSTREAM_WORKSPACE`\n   overrides the root). It refuses to touch a checkout with unrelated state,\n   fast-forwards the default branch, and creates the new branch.\n\n   Without push access to the upstream, fork it now, before anything\n   pushes: run `gh repo fork --remote` in `$workspace`, so pushes go to the\n   fork. `gh pr create` then opens the PR cross-repo by default.\n3. **Check it isn't already fixed**: `git log` in the workspace. When the\n   default branch already addresses the finding (merged, just not released),\n   tell the user and stop instead of filing.\n4. **Apply the change** in `$workspace` as ordinary editing in the upstream\n   repo. Keep it minimal and focused, and link back to the downstream context\n   in the commit body rather than in code comments.\n5. **Open the PR.** From inside `$workspace`, call the Skill tool with\n   \"open-pr\", so the upstream's own validation, self-review, and CI polling\n   run against the upstream's verification command. Leave validation,\n   self-review, and CI polling to open-pr rather than running them here. Put\n   a \"Source context\" footer in the PR body, matching the Issue mode\n   template.\n\nDone when the PR exists and you have its URL.\n\n## 6. Report\n\nTell the user the upstream repo, the mode, and the URL of the issue, PR, or\ncomment. Done when all three are reported.\n\n## Several findings at once\n\nWhen a retro produces several findings, file each as its own Issue or PR so\ntriage stays clean. Batch them only when they are genuinely one concern.\n\n## Configuration\n\n- `.claude\u002Fharness-upstream`: one line, `owner\u002Frepo`. Overrides the default\n  and the old lock file.\n- `$HARNESS_UPSTREAM`: environment override for one-off runs or CI.\n- `$HARNESS_UPSTREAM_WORKSPACE`: root for cached upstream checkouts (default\n  `${XDG_CACHE_HOME:-~\u002F.cache}\u002Fharness-issue`).\n\n## Related\n\n- `\u002Fharness retro`: surfaces upstream-worthy findings during post-session\n  review and hands each one to this skill.\n- `\u002Fharness hoist`: hoists upstream files your project has already modified.\n  This skill complements it for findings that aren't yet a code diff.\n- `\u002Fopen-pr`: runs inside the upstream workspace in PR mode.\n",{"name":5,"description":7,"allowed-tools":49,"argument-hint":50},"Bash(gh issue *), Bash(gh pr *), Bash(gh repo *), Bash(gh api *), Bash(git status), Bash(git diff *), Bash(git log *), Bash(${CLAUDE_SKILL_DIR}\u002F*), Read, Edit, Write","[issue|pr]","main","023b01bfb4a86fbf1e38a749f1044cce3e5da67d","claude-skills\u002Fharness-issue",1,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit","https:\u002F\u002Fgithub.com\u002Fdougborg","http:\u002F\u002Fdougborg.org","Platforms and Infrastructure Software Engineer","2026-11-13 07:43:37",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add dougborg\u002Fharness-kit --skill harness-issue",{"tool":66,"command":67},"bunx","bunx skills add dougborg\u002Fharness-kit --skill harness-issue",{"tool":69,"command":70},"pnpm","pnpm dlx skills add dougborg\u002Fharness-kit --skill harness-issue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fharness-issue\u002FSKILL.md",true,[74,80],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"prepare-pr-workspace.sh","SCRIPT","脚本",4125,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fharness-issue\u002Fprepare-pr-workspace.sh",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"resolve-upstream.sh",2021,"https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fharness-issue\u002Fresolve-upstream.sh",[85,104,121,153,175,192],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":96,"publishedAt":44},"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",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000039","教师与教育","PROFESSION","适用职业",[87,97,98,99,100,101,102,103],"lessons","you","with","learned","record","references","sessions",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":44},"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",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",[114,115,116,117,118,119,99,36,37,120],"logo","designer","svg logo designer","SVG","color","concepts","generate",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":133,"publishedAt":44},"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",[127,130],{"categoryNo":128,"categoryName":129,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":131,"categoryName":132,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000036","内容创作者",[134,135,136,137,138,139,140,31,141,142,143,144,145,146,147,148,149,150,151,152],"writer","documentation writer","documentation","entries","changelog","architecture","document","use","question","README","notes","code","examples","pages","for","information","guides","type","writing",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":44},"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",[],[160,161,162,163,148,164,28,99,165,166,167,168,169,170,171,172,173,174,25,145],"adhd","mode","adhd mode","next","action","output","style","progress","time","back","stop","session","reader","first","REST",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":44},"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",[],[182,183,184,99,185,186,187,188,189,190,191],"wait","wait what","re","it","missing","message","context","explain","land","last",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":44},"01M6KX43NE1NB0Y2HECY515730","to-questionnaire","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.","https:\u002F\u002Fgithub.com\u002Fdougborg\u002Fharness-kit\u002Fblob\u002Fmain\u002Fskills\u002Fthinking\u002Fto-questionnaire\u002FSKILL.md",[],[199,200,148,201,202,203,204,98,205,185,206,207],"to questionnaire","questionnaire","person","can","answer","meeting","make","async","decision"]