[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DJZNNFAQH5M6DZV74CZPEF":3,"skill-same:01M7DJZNNFAQH5M6DZV74CZPEF":44},{"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":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":43},"01M7DJZNNFAQH5M6DZV74CZPEF","maestro-wayfinder",null,"Use when an effort is too large or uncertain to specify in one session.","Orchestration-Maestro\u002Fmaestro-manifests","Orchestration-Maestro","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F322897002?v=4","01M7DJV5QYHV5358EX4AGZJZK3","01M7DJV5RPB4CBJZBKV9AHREM6",0,"MIT","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-wayfinder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: maestro-wayfinder\ndescription: \"Use when an effort is too large or uncertain to specify in one session.\"\ndisable-model-invocation: true\n---\n\n# Name the destination first\n\nEstablish what reaching the destination means through `\u002Fskill:maestro-grilling` and\n`\u002Fskill:maestro-domain-modeling`: a spec, a decision or a change. The destination fixes\nscope. This is planning by default, not permission to implement the whole effort.\nOnly an explicit override in the map's Notes carries execution into the map.\n\n## Map decisions, not implementation steps\n\nUse the [tracker's wayfinding operations](..\u002F..\u002Freferences\u002Fissue-tracker.md).\nOne issue labelled `wayfinder:map` indexes child decision tickets. Use only\n`wayfinder:` labels for this map and its tickets, not implementation triage states.\nRefer to every ticket by its linked title, not a bare number. The map is an index,\nnot a duplicate store: the resolution lives once in the ticket.\n\nKeep these map sections:\n\n- Destination: the concrete endpoint in one or two lines.\n- Notes: domain, standing preferences and skills sessions should consult.\n- Decisions so far: linked closed-ticket titles with a one-line gist.\n- Not yet specified: in-scope questions too foggy to phrase as tickets yet.\n- Out of scope: consciously excluded work and the reason it is outside this effort.\n\nOpen tickets are discovered as children, not copied into a second map inventory.\nEach ticket asks one decision-sized question and carries `wayfinder:\u003Ctype>`.\nA sharp question is a ticket even if blocked. Fog means the question cannot yet be\nphrased, not merely that its answer is unknown. Excluded work never graduates from fog.\n\n## Ticket types\n\n- `wayfinder:research` is AFK: the controller uses `\u002Fskill:maestro-research` to\n  dispatch one background researcher. The worker reads sources and returns its cited\n  file without invoking dispatching skills. Link its artifacts from the ticket. Where research\n  uses a throwaway branch, retain it as `research\u002F\u003Cname>` without merging or opening\n  a request; pushing still follows the user's permission rules.\n- `wayfinder:prototype` is HITL: use `\u002Fskill:maestro-prototype` so the human can react\n  to a concrete artifact. Link that artifact as evidence.\n- `wayfinder:grilling` is HITL: use grilling and domain modeling to settle the question\n  with the human, never by simulating their answer.\n- `wayfinder:task` is HITL or AFK: do prerequisite work that makes a decision possible,\n  such as provisioning access. Give a precise human checklist where needed. Record\n  resulting facts and authorized credential locations, not secrets.\n\n## Chart a new map\n\n1. Name the destination, then grill breadth-first across the space. If the route is\n   already clear with no fog, ask how to proceed instead of manufacturing a map.\n2. Create the map and all currently sharp child questions. Leave the rest as fog.\n3. In a second pass, wire native blocking edges and cross-references using real ids.\n   Use the tracker's fallback only when native blocking is unavailable. Never publish\n   placeholder issue links that could point to unrelated tickets.\n4. Launch independent research with self-contained briefs and artifact locations.\n   Stop after charting; do not hand-resolve the human decisions in the same session.\n\n## Work through an existing map\n\nRead the map and Notes first, then the selected ticket's label and body. Use a named\nticket when supplied; otherwise take the first open, unblocked, unclaimed child in\nmap order, then number order. Claim by assignment as the first write before work.\nA frontier ticket has no open blockers and no assignee. Other sessions may be active.\n\nWork one non-research ticket per session; independent research is the exception.\nFetch related resolutions only as needed. Apply the ticket type's method and let the\nhuman speak for themselves. Record the answer as a resolution comment, close the\nissue and append a named pointer in Decisions so far. Graduate newly sharp fog into\nnew tickets using create-then-wire; remove its old fog entry.\n\nIf a decision invalidates tickets, update or remove them. If a ticket proves out of\nscope, close it with the reason and link it from Out of scope, not Decisions so far.\nWhen no fog or open decisions remain, hand off to `\u002Fskill:maestro-to-spec` and\n`\u002Fskill:maestro-to-tickets` rather than silently starting a large build. Requests that\nneed ordinary implementation triage can enter through `\u002Fskill:maestro-triage` when\nthe user chooses that next phase.\n","# Name the destination first\n\nEstablish what reaching the destination means through `\u002Fskill:maestro-grilling` and\n`\u002Fskill:maestro-domain-modeling`: a spec, a decision or a change. The destination fixes\nscope. This is planning by default, not permission to implement the whole effort.\nOnly an explicit override in the map's Notes carries execution into the map.\n\n## Map decisions, not implementation steps\n\nUse the [tracker's wayfinding operations](..\u002F..\u002Freferences\u002Fissue-tracker.md).\nOne issue labelled `wayfinder:map` indexes child decision tickets. Use only\n`wayfinder:` labels for this map and its tickets, not implementation triage states.\nRefer to every ticket by its linked title, not a bare number. The map is an index,\nnot a duplicate store: the resolution lives once in the ticket.\n\nKeep these map sections:\n\n- Destination: the concrete endpoint in one or two lines.\n- Notes: domain, standing preferences and skills sessions should consult.\n- Decisions so far: linked closed-ticket titles with a one-line gist.\n- Not yet specified: in-scope questions too foggy to phrase as tickets yet.\n- Out of scope: consciously excluded work and the reason it is outside this effort.\n\nOpen tickets are discovered as children, not copied into a second map inventory.\nEach ticket asks one decision-sized question and carries `wayfinder:\u003Ctype>`.\nA sharp question is a ticket even if blocked. Fog means the question cannot yet be\nphrased, not merely that its answer is unknown. Excluded work never graduates from fog.\n\n## Ticket types\n\n- `wayfinder:research` is AFK: the controller uses `\u002Fskill:maestro-research` to\n  dispatch one background researcher. The worker reads sources and returns its cited\n  file without invoking dispatching skills. Link its artifacts from the ticket. Where research\n  uses a throwaway branch, retain it as `research\u002F\u003Cname>` without merging or opening\n  a request; pushing still follows the user's permission rules.\n- `wayfinder:prototype` is HITL: use `\u002Fskill:maestro-prototype` so the human can react\n  to a concrete artifact. Link that artifact as evidence.\n- `wayfinder:grilling` is HITL: use grilling and domain modeling to settle the question\n  with the human, never by simulating their answer.\n- `wayfinder:task` is HITL or AFK: do prerequisite work that makes a decision possible,\n  such as provisioning access. Give a precise human checklist where needed. Record\n  resulting facts and authorized credential locations, not secrets.\n\n## Chart a new map\n\n1. Name the destination, then grill breadth-first across the space. If the route is\n   already clear with no fog, ask how to proceed instead of manufacturing a map.\n2. Create the map and all currently sharp child questions. Leave the rest as fog.\n3. In a second pass, wire native blocking edges and cross-references using real ids.\n   Use the tracker's fallback only when native blocking is unavailable. Never publish\n   placeholder issue links that could point to unrelated tickets.\n4. Launch independent research with self-contained briefs and artifact locations.\n   Stop after charting; do not hand-resolve the human decisions in the same session.\n\n## Work through an existing map\n\nRead the map and Notes first, then the selected ticket's label and body. Use a named\nticket when supplied; otherwise take the first open, unblocked, unclaimed child in\nmap order, then number order. Claim by assignment as the first write before work.\nA frontier ticket has no open blockers and no assignee. Other sessions may be active.\n\nWork one non-research ticket per session; independent research is the exception.\nFetch related resolutions only as needed. Apply the ticket type's method and let the\nhuman speak for themselves. Record the answer as a resolution comment, close the\nissue and append a named pointer in Decisions so far. Graduate newly sharp fog into\nnew tickets using create-then-wire; remove its old fog entry.\n\nIf a decision invalidates tickets, update or remove them. If a ticket proves out of\nscope, close it with the reason and link it from Out of scope, not Decisions so far.\nWhen no fog or open decisions remain, hand off to `\u002Fskill:maestro-to-spec` and\n`\u002Fskill:maestro-to-tickets` rather than silently starting a large build. Requests that\nneed ordinary implementation triage can enter through `\u002Fskill:maestro-triage` when\nthe user chooses that next phase.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","f33b1a1de12042270a260ffdddd74b67671a1d9a","manifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-wayfinder","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro","Automated guardrails for faster, better, more maintainable and more secure code. Our Northstar: never reached, always pursued.","2026-11-09 01:08:53",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-wayfinder",{"tool":37,"command":38},"bunx","bunx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-wayfinder",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Orchestration-Maestro\u002Fmaestro-manifests --skill maestro-wayfinder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Fmaestro-skills\u002Fskills\u002Fmaestro-wayfinder\u002FSKILL.md",[],[45,52,57,62,67,72],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M7DK0KB6JRRJRQPMXG075AQ6","audit","Fixture skill.","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-without-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fsecurity\u002Fscan\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":53,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M7DK0JAQG1J25DG064S7PR27","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-without-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":58,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M7DK0HBNY88V2B7PF5E4JWZS","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-with-empty-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fsecurity\u002Fscan\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":63,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7DK0G9CB5MFGRD73SNEXXYE","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-with-empty-name-takes-its-folder-name\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":68,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7DK0FA198RVD2KCEW9YDQ6K","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-in-dot-folder-is-skipped\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002Faudit\u002FSKILL.md",[],[],{"skillNo":73,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7DK0EAZVV9A5CN27PD2MTMB","https:\u002F\u002Fgithub.com\u002FOrchestration-Maestro\u002Fmaestro-manifests\u002Fblob\u002Fmain\u002Ftests\u002Fscorecard_cases\u002Fskill-in-dot-folder-is-skipped\u002Fmanifests\u002Fcapabilities\u002Fpractice\u002Freview\u002Fskills\u002F.drafts\u002Faudit\u002FSKILL.md",[],[]]