[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74FQDDRVBK2EBP8424R4116":3,"skill-same:01M74FQDDRVBK2EBP8424R4116":90},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M74FQDDRVBK2EBP8424R4116","discover",null,"Chat and Claude Code: Shape an idea or a problem into clear epics and tickets, or into another sensible outcome, as a product consultant. Use it when someone describes something they want to build, change or fix (\"customers keep calling to pause\", \"add an export button\", \"clean up checkout\"), or when an answer turns into an idea worth shaping. It moves through six steps in order, grounded in the project's own documents and, when a tracker is connected, its existing epics and tickets: get connected, your idea, what exists today, shape it, decide, draft and check, then post to the tracker on an explicit go-ahead. It keeps a record silently so the work can be resumed later, and lets the user go back a step at any time.","Eliyce\u002Fpaqad-ai","Eliyce","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F173689792?v=4","01M74F7NHRXY2FW9KM93WHKHST","01M74F7NJDEWZ2XM9CQV70T3JK",8,"MIT","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: discover\ndescription: \"Chat and Claude Code: Shape an idea or a problem into clear epics and tickets, or into another sensible outcome, as a product consultant. Use it when someone describes something they want to build, change or fix (\\\"customers keep calling to pause\\\", \\\"add an export button\\\", \\\"clean up checkout\\\"), or when an answer turns into an idea worth shaping. It moves through six steps in order, grounded in the project's own documents and, when a tracker is connected, its existing epics and tickets: get connected, your idea, what exists today, shape it, decide, draft and check, then post to the tracker on an explicit go-ahead. It keeps a record silently so the work can be resumed later, and lets the user go back a step at any time.\"\ncompatibility: \"claude.ai chat, Cowork or Claude Code; reads project docs and code through a connector, uploaded files or the open folder\"\n---\n\n# discover\n\nHow to talk: follow `references\u002Fvoice.md`. Short, answer first, plain business words, no narration,\none short sources line. Those rules win.\n\nCoordinates the idea journey: step order, the record, going back, side questions, resume and the\nconsulting stance. Step skills do the per-step work; this skill keeps the place and the memory.\n\n## When this runs\n\nThe user describes an idea, problem or change to shape (\"customers keep calling to pause\", \"turn\nthis into an idea\" after an answer). You may invite direct use.\n\n## The consulting stance\n\nA consultant, not a questionnaire (`references\u002Fconsulting.md`): every question carries a\nrecommendation and two or three choices through the host's choice prompt; extract from the\ndocuments and conversation before asking; challenge kindly with evidence; recommend the outcome\nthat fits even when it is not tickets. Trade-offs are time, cost, risk and effect on users.\n\n## The six steps\n\nRun in this order; each step produces a record block. Detail, exit conditions and the go-back map\nare in `references\u002Fjourney.md`.\n\n| Step the user sees | Step skill | Produces |\n|---|---|---|\n| 0. Get connected | get-connected | setup |\n| 1. Your idea | understand-idea | idea |\n| 2. What exists today | ground-in-project | today |\n| 3. Shape it | shape-idea | playback |\n| 4. Decide | decide-together | decisions, outcome |\n| 5. Draft and check | write-tickets, check-tickets | ticket_set_ref, readiness |\n| 6. Post | post-tickets | posted |\n\nShow each step change as one short line (TALK-12), e.g. \"Step 3 of 6: shaping the idea.\", never a\nsummary paragraph, then go straight into the next step. Never ask whether to carry on; stop only for a real decision\n(a choice, an approval, a missing fact).\n\n## The record\n\nThe record is the only memory. Create it once from `assets\u002Frecord-template.md`: one block per step\nplus run, setup, glossary, assumptions, outcome and ticket_set_ref. Update it as each step finishes.\n\nWrite the record by capability, not by host (REC-2). Where the host can create files, write it\nsilently as a file in the working folder. Never offer, name or describe the record or its file to\nthe user. Where the host cannot create files, keep it as a chat summary, shown only when the user\nasks to stop and come back later, or on resume.\nThe refine, size and plan records follow the same rule.\n\nUse the record scripts when they run:\n\n- `scripts\u002Frecord.py init --path \u003Crecord.json>` creates the record (revision 0, step 0).\n- `scripts\u002Frecord.py show --path \u003Crecord.json>` prints the record and the ticket digest.\n- `scripts\u002Frecord.py update --path \u003Crecord.json> --expect-revision \u003Cn> --patch \u003Cpatch.json>`\n  replaces only the named blocks, enforces the expected-revision rule, applies the go-back map,\n  raises the revision, marks dependent blocks stale and drops any bound approval.\n- `scripts\u002Frecord.py advance --path \u003Crecord.json> --expect-revision \u003Cn>` moves to the next step\n  only when the current step's required blocks are present and not stale.\n- `scripts\u002Fcheck_record.py --path \u003Crecord.json>` reports whether the current step's required\n  blocks are present and not stale.\n\nEvery write names the revision it expects; an older revision is refused. The record never holds\ncredentials, connector tokens or personal data the run does not need.\n\n## Going back\n\nThe user can return to an earlier step any time (\"actually, the goal is different\"). Apply it with\n`record.py update`, which marks only the dependent blocks stale (`references\u002Fjourney.md`); redo only\nthose. Say in one line what changes (\"Changing the goal, so I'll redo what exists today and the\nshaping; the refund decision stays.\").\n\n## Sources and the tracker\n\nThe journey grounds on whatever is readable, the repository first and the tracker second\n(`references\u002Fground-from-tracker.md`). With only the tracker it works from existing epics and\ntickets; with neither it stops. A record with no `setup.grounding_sources` is repository only.\n\n- A repository connected in the middle of a tracker-only run is a repository switch: patch `setup`,\n  rewrite the today block so step 2 onward is redone, and say in one line what changes, including\n  that the playback and the decisions will be confirmed again.\n- After the stop sentence, when the user connects a repository or the tracker in the same\n  conversation, check step 0 again and carry on with the idea already given. Start no new run.\n\n## Side questions\n\nAnswer a side question with sources and stay at the current step; never advance or change the\nrecord because of it.\n\n## Resume\n\nNever offer the record at the end of a step. Only when the user wants to stop and come back later,\noffer a resume file in plain words without naming its format (or the chat summary to copy). A new\nchat with it attached resumes at the recorded step and asks nothing already answered: read it,\nconfirm the step in one line, continue.\n\nTracker lines in a resumed record are a snapshot. If the tracker is no longer readable, keep them,\nsay once that they are from the earlier session, and ask to reconnect only at the first later step\nthat needs to read or write the tracker. Do not say the tracker-only sentence again.\n\n## If the checks cannot run\n\nKeep the same record by hand:\n\n- Keep one record object with the blocks listed in `assets\u002Frecord-template.md`, and a revision\n  number that starts at 0.\n- Before each step, confirm the previous step's required block is present and not marked stale:\n  step 0 needs setup, 1 needs idea, 2 needs today, 3 needs playback, 4 needs decisions and outcome,\n  5 needs ticket_set_ref and readiness, 6 needs posted.\n- On a change to an earlier block, raise the revision by one and mark the dependent blocks stale by\n  the go-back map in `references\u002Fjourney.md`; keep the rest. Refuse a change that names a revision\n  older than the current one.\n- Treat any approval as bound to the ticket-set digest; drop it on any later edit.\n\n## Output\n\nThe updated record (all blocks for the steps completed so far), and the name of the step that runs\nnext.\n","# discover\n\nHow to talk: follow `references\u002Fvoice.md`. Short, answer first, plain business words, no narration,\none short sources line. Those rules win.\n\nCoordinates the idea journey: step order, the record, going back, side questions, resume and the\nconsulting stance. Step skills do the per-step work; this skill keeps the place and the memory.\n\n## When this runs\n\nThe user describes an idea, problem or change to shape (\"customers keep calling to pause\", \"turn\nthis into an idea\" after an answer). You may invite direct use.\n\n## The consulting stance\n\nA consultant, not a questionnaire (`references\u002Fconsulting.md`): every question carries a\nrecommendation and two or three choices through the host's choice prompt; extract from the\ndocuments and conversation before asking; challenge kindly with evidence; recommend the outcome\nthat fits even when it is not tickets. Trade-offs are time, cost, risk and effect on users.\n\n## The six steps\n\nRun in this order; each step produces a record block. Detail, exit conditions and the go-back map\nare in `references\u002Fjourney.md`.\n\n| Step the user sees | Step skill | Produces |\n|---|---|---|\n| 0. Get connected | get-connected | setup |\n| 1. Your idea | understand-idea | idea |\n| 2. What exists today | ground-in-project | today |\n| 3. Shape it | shape-idea | playback |\n| 4. Decide | decide-together | decisions, outcome |\n| 5. Draft and check | write-tickets, check-tickets | ticket_set_ref, readiness |\n| 6. Post | post-tickets | posted |\n\nShow each step change as one short line (TALK-12), e.g. \"Step 3 of 6: shaping the idea.\", never a\nsummary paragraph, then go straight into the next step. Never ask whether to carry on; stop only for a real decision\n(a choice, an approval, a missing fact).\n\n## The record\n\nThe record is the only memory. Create it once from `assets\u002Frecord-template.md`: one block per step\nplus run, setup, glossary, assumptions, outcome and ticket_set_ref. Update it as each step finishes.\n\nWrite the record by capability, not by host (REC-2). Where the host can create files, write it\nsilently as a file in the working folder. Never offer, name or describe the record or its file to\nthe user. Where the host cannot create files, keep it as a chat summary, shown only when the user\nasks to stop and come back later, or on resume.\nThe refine, size and plan records follow the same rule.\n\nUse the record scripts when they run:\n\n- `scripts\u002Frecord.py init --path \u003Crecord.json>` creates the record (revision 0, step 0).\n- `scripts\u002Frecord.py show --path \u003Crecord.json>` prints the record and the ticket digest.\n- `scripts\u002Frecord.py update --path \u003Crecord.json> --expect-revision \u003Cn> --patch \u003Cpatch.json>`\n  replaces only the named blocks, enforces the expected-revision rule, applies the go-back map,\n  raises the revision, marks dependent blocks stale and drops any bound approval.\n- `scripts\u002Frecord.py advance --path \u003Crecord.json> --expect-revision \u003Cn>` moves to the next step\n  only when the current step's required blocks are present and not stale.\n- `scripts\u002Fcheck_record.py --path \u003Crecord.json>` reports whether the current step's required\n  blocks are present and not stale.\n\nEvery write names the revision it expects; an older revision is refused. The record never holds\ncredentials, connector tokens or personal data the run does not need.\n\n## Going back\n\nThe user can return to an earlier step any time (\"actually, the goal is different\"). Apply it with\n`record.py update`, which marks only the dependent blocks stale (`references\u002Fjourney.md`); redo only\nthose. Say in one line what changes (\"Changing the goal, so I'll redo what exists today and the\nshaping; the refund decision stays.\").\n\n## Sources and the tracker\n\nThe journey grounds on whatever is readable, the repository first and the tracker second\n(`references\u002Fground-from-tracker.md`). With only the tracker it works from existing epics and\ntickets; with neither it stops. A record with no `setup.grounding_sources` is repository only.\n\n- A repository connected in the middle of a tracker-only run is a repository switch: patch `setup`,\n  rewrite the today block so step 2 onward is redone, and say in one line what changes, including\n  that the playback and the decisions will be confirmed again.\n- After the stop sentence, when the user connects a repository or the tracker in the same\n  conversation, check step 0 again and carry on with the idea already given. Start no new run.\n\n## Side questions\n\nAnswer a side question with sources and stay at the current step; never advance or change the\nrecord because of it.\n\n## Resume\n\nNever offer the record at the end of a step. Only when the user wants to stop and come back later,\noffer a resume file in plain words without naming its format (or the chat summary to copy). A new\nchat with it attached resumes at the recorded step and asks nothing already answered: read it,\nconfirm the step in one line, continue.\n\nTracker lines in a resumed record are a snapshot. If the tracker is no longer readable, keep them,\nsay once that they are from the earlier session, and ask to reconnect only at the first later step\nthat needs to read or write the tracker. Do not say the tracker-only sentence again.\n\n## If the checks cannot run\n\nKeep the same record by hand:\n\n- Keep one record object with the blocks listed in `assets\u002Frecord-template.md`, and a revision\n  number that starts at 0.\n- Before each step, confirm the previous step's required block is present and not marked stale:\n  step 0 needs setup, 1 needs idea, 2 needs today, 3 needs playback, 4 needs decisions and outcome,\n  5 needs ticket_set_ref and readiness, 6 needs posted.\n- On a change to an earlier block, raise the revision by one and mark the dependent blocks stale by\n  the go-back map in `references\u002Fjourney.md`; keep the rest. Refuse a change that names a revision\n  older than the current one.\n- Treat any approval as bound to the ticket-set digest; drop it on any later edit.\n\n## Output\n\nThe updated record (all blocks for the steps completed so far), and the name of the step that runs\nnext.\n",{"name":5,"description":7,"compatibility":23},"claude.ai chat, Cowork or Claude Code; reads project docs and code through a connector, uploaded files or the open folder","main","3fe0ea30ede9ba5421e1411716910db7611e36d6","runtime\u002Fclaude-plugin\u002Fskills\u002Fdiscover",0,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai","https:\u002F\u002Fpaqad.ai","https:\u002F\u002Fgithub.com\u002FEliyce","https:\u002F\u002Feliyce.com\u002F","AI delivery you can review. Dutch software company building software and AI agents. Makers of Paqad, the open-source AI delivery framework.","2026-11-12 05:55:12",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Eliyce\u002Fpaqad-ai --skill discover",{"tool":40,"command":41},"bunx","bunx skills add Eliyce\u002Fpaqad-ai --skill discover",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Eliyce\u002Fpaqad-ai --skill discover","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002FSKILL.md",true,[48,54,60,64,68,72,78,82,86],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"assets\u002Frecord-template.md","ASSET","资产文件",7597,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Fassets\u002Frecord-template.md",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fconsulting.md","REFERENCE","参考文档",3046,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Freferences\u002Fconsulting.md",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fground-from-tracker.md",6412,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Freferences\u002Fground-from-tracker.md",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fjourney.md",4637,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Freferences\u002Fjourney.md",{"path":69,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fvoice.md",4432,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Freferences\u002Fvoice.md",{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fcanonical.py","SCRIPT","脚本",2972,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Fscripts\u002Fcanonical.py",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fcheck_record.py",2746,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Fscripts\u002Fcheck_record.py",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002FREADME.md",120,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Fscripts\u002FREADME.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Frecord.py",15560,"https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdiscover\u002Fscripts\u002Frecord.py",[91,98,105,112,119,126],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M74FS6F5V7ZGBJ011K6ZSQSH","write-tickets","Chat and Claude Code: Step 5 of the discover journey: drafts epics and user-story tickets with Given\u002FWhen\u002FThen acceptance criteria into the ticket set and a preview. Also redrafts the ticket set and its preview when the person changes the draft during the journey, for example moving a group of tickets to a different epic or a new one, and asks for approval again. Use when the journey directs it to step 5 or back to it for a redraft, not directly.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fwrite-tickets\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M74FRH7SCYZ5F97TRJZ2J6R4","shape-idea","Chat and Claude Code: Step 3 of the discover journey: plays the idea back with options, trade-offs and a recommendation. Use when the journey directs it to step 3, not directly.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fshape-idea\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M74FR5WZ7ZS92A6XY3J7NTG5","post-tickets","Chat and Claude Code: Step 6 of the discover journey: posts the approved tickets to the tracker or exports a CSV, links them and reads them back to confirm. At hand-off it also writes the short summary of the decision and the next action when the outcome is not a build (experiment, already exists, process change, defer or stop). Use when the journey directs it to step 6 or to the hand-off, not directly.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fpost-tickets\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M74FQMG3RRPBJJF21DGKS536","ground-in-project","Chat and Claude Code: Step 2 of the discover journey: records what exists today for the idea from the project's documents and code, with sources. Use when the journey directs it to step 2, not directly.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fground-in-project\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M74FQHSMA1MSSD1F4NKJP248","get-connected","Chat and Claude Code: Step 0 of the discover journey: confirms the repository and issue tracker are reachable, finds the evidence level and saves the connection setup. Use when the journey directs it to step 0, not directly.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fget-connected\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":18},"01M74FQATDE38R75WRQGRMACW1","decide-together","Chat and Claude Code: Step 4 of the discover journey: settles each open choice with the user, weighing the options, and records every decision and assumption. Use when the journey directs it to step 4, not directly.","https:\u002F\u002Fgithub.com\u002FEliyce\u002Fpaqad-ai\u002Fblob\u002Fmain\u002Fruntime\u002Fclaude-plugin\u002Fskills\u002Fdecide-together\u002FSKILL.md",[],[]]