[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77YCSJVXWMQWMMTXMY9YT91":3,"skill-same:01M77YCSJVXWMQWMMTXMY9YT91":47},{"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":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M77YCSJVXWMQWMMTXMY9YT91","decision-mapping",null,"Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.","503496348-ops\u002Fmischief-production","503496348-ops","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266905914?v=4","01M77X5J7XQWWZGT8998HDGXQM","AtomCollide","01M77X5J8V78Y3NXMY6BBC75X9",2,"MIT","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fmp-in-progress\u002Fdecision-mapping\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: decision-mapping\ndescription: Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.\ndisable-model-invocation: true\n---\n\nThis skill is invoked when a loose idea requires more than one agent session to turn into a plan. It creates a stateful decision map in a markdown file, and drives the user through a sequence of tickets to resolve the open questions - which may require either prototyping, research or grilling.\n\n## The Decision Map\n\nThe decision map is a single compact Markdown file, one per planning effort, git-tracked alongside the project. It is the canonical artifact — the **whole map is loaded as context into every session**, so it must stay compact.\n\nAssets created during tickets should be linked to from the map, not duplicated within it.\n\n### Structure\n\nEntries (\"tickets\"), each its own section keyed by a short dash-case slug that\nreads as a mini-title (e.g. `relational-db`, `auth-strategy`, `cache-layer`) —\nterse enough to stay token-efficient, and unique within the map.\n\n```markdown\n## relational-db: Relational Or Non-Relational Database?\n\nBlocked by: \u003Cslug>, \u003Cslug>\nStatus: open | in-progress | resolved\nType: Research | Prototype | Grilling\n\n### Question\n\n\u003Cquestion-here>\n\n### Answer\n\n\u003Canswer-here>\n```\n\nThe slug is the canonical id, used in every `Blocked by` edge and prose\nreference; the title after the colon is optional. A ticket\nis **unblocked** when every ticket in its `Blocked by` list is `resolved`. A\nsession **claims** its ticket by setting `Status: in-progress` and saving the map\nbefore any work, so concurrent sessions skip it.\n\nEach ticket must be sized to one 100K token agent session.\n\n## Ticket Types\n\nThere are three types of tickets:\n\n- **Research**: Reading documentation, third-party API's, or local resources like knowledge bases. Creates a markdown summary as an asset. Use this when knowledge outside the current working directory is required.\n- **Prototype**: Writing UI or logic code to test a hypothesis, or to explore a design space. Uses the \u002Fprototype skill. Creates a prototype as an asset. Use this when \"how should it look\" or \"how should it behave\" is the key question.\n- **Grilling**: Conversation with the agent. Uses the \u002Fgrilling and \u002Fdomain-modeling skills. Asks one question at a time. The default case.\n\n## Fog of war\n\nThe map is _deliberately_ incomplete beyond the frontier. Your job is to investigate the frontier, and to resolve tickets in order to push the frontier forward. Push back the fog of war, one node at a time — until the path to the finish line is clear and no tickets remain.\n\n## Invocation\n\nTwo branches. Either way, **every session ends with a [Handoff](#handoff)** — never resolve more than one ticket per session.\n\n### Create the map\n\nUser invokes with a loose idea.\n\n1. Run a `\u002Fgrilling` and `\u002Fdomain-modeling` session to surface the open decisions. Ask one question at a time.\n2. Write a new decision map — mostly fog, frontier identified, trivially-decidable entries resolved inline.\n3. Handoff. Map-building is one session's work; do not also resolve tickets.\n\n### Work through the map\n\nUser invokes with a path to an existing map. A ticket slug is **optional** — without one, you pick the next decision, not the user.\n\n1. Load the **whole map** as context.\n2. Choose the ticket. If the user named one, use it. Otherwise pick the first `open` ticket in document order that is [unblocked](#structure). [Claim it](#structure): set `Status: in-progress` and save before any work.\n3. Resolve it, invoking skills as needed. If in doubt, use `\u002Fgrilling` and `\u002Fdomain-modeling`.\n4. Record the answer in the ticket's body and set `Status: resolved`.\n5. Add newly-discovered tickets with correct `Blocked by` edges. If the decisions made invalidate other parts of the map, update or delete those nodes.\n6. Handoff.\n\nThe user may run unblocked tickets in parallel, so expect other agents to be editing the map in their own sessions.\n\n## Handoff\n\nEnd every session by clearing the context and opening one or more fresh sessions. Close with a **Next steps** block the user can copy-paste. Two cases:\n\n**Open tickets remain.** List the currently-unblocked tickets, then give two copy-paste options: a bare command for one session (you pick the next ticket), and one pinned command per unblocked ticket for running them in parallel. Paste one line per fresh window — opening one, some, or all of them.\n\n> **Next steps** — 3 tickets unblocked: `auth-strategy`, `cache-layer`, `rate-limits`.\n> Clear the context, then open fresh sessions.\n>\n> **One session** — resolves the next unblocked ticket:\n> ```\n> Invoke \u002Fdecision-mapping with the map at \u003Cpath>.\n> ```\n>\n> **Parallel** — paste one line per window, up to all 3:\n> ```\n> Invoke \u002Fdecision-mapping with the map at \u003Cpath>, ticket auth-strategy.\n> Invoke \u002Fdecision-mapping with the map at \u003Cpath>, ticket cache-layer.\n> Invoke \u002Fdecision-mapping with the map at \u003Cpath>, ticket rate-limits.\n> ```\n\n**No open tickets remain.** The fog is pushed back far enough that the path to the finish line is clear — the map is done. (The initial grilling may also surface no fog at all, in which case there was never a map to build.) Recommend implementing directly, or using `\u002Fto-prd` to schedule a multi-session implementation.\n","This skill is invoked when a loose idea requires more than one agent session to turn into a plan. It creates a stateful decision map in a markdown file, and drives the user through a sequence of tickets to resolve the open questions - which may require either prototyping, research or grilling.\n\n## The Decision Map\n\nThe decision map is a single compact Markdown file, one per planning effort, git-tracked alongside the project. It is the canonical artifact — the **whole map is loaded as context into every session**, so it must stay compact.\n\nAssets created during tickets should be linked to from the map, not duplicated within it.\n\n### Structure\n\nEntries (\"tickets\"), each its own section keyed by a short dash-case slug that\nreads as a mini-title (e.g. `relational-db`, `auth-strategy`, `cache-layer`) —\nterse enough to stay token-efficient, and unique within the map.\n\n```markdown\n## relational-db: Relational Or Non-Relational Database?\n\nBlocked by: \u003Cslug>, \u003Cslug>\nStatus: open | in-progress | resolved\nType: Research | Prototype | Grilling\n\n### Question\n\n\u003Cquestion-here>\n\n### Answer\n\n\u003Canswer-here>\n```\n\nThe slug is the canonical id, used in every `Blocked by` edge and prose\nreference; the title after the colon is optional. A ticket\nis **unblocked** when every ticket in its `Blocked by` list is `resolved`. A\nsession **claims** its ticket by setting `Status: in-progress` and saving the map\nbefore any work, so concurrent sessions skip it.\n\nEach ticket must be sized to one 100K token agent session.\n\n## Ticket Types\n\nThere are three types of tickets:\n\n- **Research**: Reading documentation, third-party API's, or local resources like knowledge bases. Creates a markdown summary as an asset. Use this when knowledge outside the current working directory is required.\n- **Prototype**: Writing UI or logic code to test a hypothesis, or to explore a design space. Uses the \u002Fprototype skill. Creates a prototype as an asset. Use this when \"how should it look\" or \"how should it behave\" is the key question.\n- **Grilling**: Conversation with the agent. Uses the \u002Fgrilling and \u002Fdomain-modeling skills. Asks one question at a time. The default case.\n\n## Fog of war\n\nThe map is _deliberately_ incomplete beyond the frontier. Your job is to investigate the frontier, and to resolve tickets in order to push the frontier forward. Push back the fog of war, one node at a time — until the path to the finish line is clear and no tickets remain.\n\n## Invocation\n\nTwo branches. Either way, **every session ends with a [Handoff](#handoff)** — never resolve more than one ticket per session.\n\n### Create the map\n\nUser invokes with a loose idea.\n\n1. Run a `\u002Fgrilling` and `\u002Fdomain-modeling` session to surface the open decisions. Ask one question at a time.\n2. Write a new decision map — mostly fog, frontier identified, trivially-decidable entries resolved inline.\n3. Handoff. Map-building is one session's work; do not also resolve tickets.\n\n### Work through the map\n\nUser invokes with a path to an existing map. A ticket slug is **optional** — without one, you pick the next decision, not the user.\n\n1. Load the **whole map** as context.\n2. Choose the ticket. If the user named one, use it. Otherwise pick the first `open` ticket in document order that is [unblocked](#structure). [Claim it](#structure): set `Status: in-progress` and save before any work.\n3. Resolve it, invoking skills as needed. If in doubt, use `\u002Fgrilling` and `\u002Fdomain-modeling`.\n4. Record the answer in the ticket's body and set `Status: resolved`.\n5. Add newly-discovered tickets with correct `Blocked by` edges. If the decisions made invalidate other parts of the map, update or delete those nodes.\n6. Handoff.\n\nThe user may run unblocked tickets in parallel, so expect other agents to be editing the map in their own sessions.\n\n## Handoff\n\nEnd every session by clearing the context and opening one or more fresh sessions. Close with a **Next steps** block the user can copy-paste. Two cases:\n\n**Open tickets remain.** List the currently-unblocked tickets, then give two copy-paste options: a bare command for one session (you pick the next ticket), and one pinned command per unblocked ticket for running them in parallel. Paste one line per fresh window — opening one, some, or all of them.\n\n> **Next steps** — 3 tickets unblocked: `auth-strategy`, `cache-layer`, `rate-limits`.\n> Clear the context, then open fresh sessions.\n>\n> **One session** — resolves the next unblocked ticket:\n> ```\n> Invoke \u002Fdecision-mapping with the map at \u003Cpath>.\n> ```\n>\n> **Parallel** — paste one line per window, up to all 3:\n> ```\n> Invoke \u002Fdecision-mapping with the map at \u003Cpath>, ticket auth-strategy.\n> Invoke \u002Fdecision-mapping with the map at \u003Cpath>, ticket cache-layer.\n> Invoke \u002Fdecision-mapping with the map at \u003Cpath>, ticket rate-limits.\n> ```\n\n**No open tickets remain.** The fog is pushed back far enough that the path to the finish line is clear — the map is done. (The initial grilling may also surface no fog at all, in which case there was never a map to build.) Recommend implementing directly, or using `\u002Fto-prd` to schedule a multi-session implementation.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","c9103dbad48ef3005f163584d0f2abd4591217f6","skills\u002Fmp-in-progress\u002Fdecision-mapping",1,"https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production","https:\u002F\u002Fgithub.com\u002F503496348-ops","https:\u002F\u002F503496348-ops.github.io\u002Fatomcollide-product-matrix\u002F#tree","元素碰撞-AtomCollide-AI 智能体实验室 测试人专属成长社群 正式招募\r\n我们的目标很纯粹：连接每一位测试工程师\u002FAI使用探索与爱好者，让你在这里既能扎实打磨技术硬实力，也能打通职业晋升的新通路，这是一个专注于AI领域的开源组","2026-07-30 00:35:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add 503496348-ops\u002Fmischief-production --skill decision-mapping",{"tool":40,"command":41},"bunx","bunx skills add 503496348-ops\u002Fmischief-production --skill decision-mapping",{"tool":43,"command":44},"pnpm","pnpm dlx skills add 503496348-ops\u002Fmischief-production --skill decision-mapping","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fmp-in-progress\u002Fdecision-mapping\u002FSKILL.md",[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M77YG7NPZHE751W9QGK3H9ED","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-skills\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M77YG4HPYH0GJP974DZ6KCPQ","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-writing-plans\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M77YFZW1FZ1GVC5C89NPE5M8","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-verification-before-completion\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M77YFVPWANT5VE5GWBTKHPA2","using-智械工程","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-superpowers\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M77YFQJAW5PX3QYSBCD3B24S","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M77YFMSTB70VX8W2QHNJWYB0","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002F503496348-ops\u002Fmischief-production\u002Fblob\u002Fmain\u002Fskills\u002Fsp-test-driven-development\u002FSKILL.md",[],[]]