[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CP5VTT6TAGWJCKSMEFMBXM":3,"skill-same:01M7CP5VTT6TAGWJCKSMEFMBXM":57},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7CP5VTT6TAGWJCKSMEFMBXM","create-repository",null,"Interview the maintainer and create a repository, optionally adopt repository standards, then route its vision to a small design interview or a planning map.","lutzseverino\u002Frepo-canon","lutzseverino","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F28309837?v=4","01M77NN0YKH0YYGY7W7ER23MX0","Jasper","01M7CP5B58PDMK3RT3CE7F70Q2",1,"MIT","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-repository\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: create-repository\ndescription: Interview the maintainer and create a repository, optionally adopt repository standards, then route its vision to a small design interview or a planning map.\ndisable-model-invocation: false\n---\n\nA prompt or brief naming this skill is its invocation.\n\nOwn the founding interview and creation. Delegate adoption to the separately\ninstalled `adopt-repository-standards` skill; delegate vision to `grill-with-docs`\nor `wayfinder`. Check the chosen route's dependencies before invoking it. The\nsmall route needs `grill-with-docs`, `grilling` and `domain-modeling`; Wayfinder\nalso needs `research` and `prototype`. If a required skill is missing, report\nits name and pause that step for installation, retaining the completed work.\n\n## Interview\n\nAsk one question at a time, proposing an answer from what the person has said\nand waiting for confirmation. Where there is no basis for a proposal, ask for\nthe value; invent no namespace, visibility, location or license. Reuse supplied\nanswers. If the interview shows the work belongs in an existing repository or\nneeds no repository, stop before creating anything.\n\nSettle these in order:\n\n1. Repository name and one-line purpose.\n2. Hosting namespace and visibility, unless the person chose local-only. If no\n   authenticated hosting-platform tool or credential is supplied, explain the\n   local fallback and skip remote questions that cannot be used.\n3. Parent directory. Resolve the proposed destination and check it and its\n   existing ancestors with Git, including linked worktrees and bare repositories.\n   Refuse a destination inside an existing Git work tree. Propose the current\n   directory as the parent only when it is outside every Git work tree, and\n   have the person confirm it. Use a new empty destination; preserve existing\n   content.\n4. License, including “none for now.” Keep the answer for adoption's contextual\n   work; this skill never chooses one or creates a license on the non-adoption\n   path.\n5. Whether to adopt repository standards. When invoked with adoption on (as\n   `create-adopted-repo` does), keep it on and skip this question.\n6. Vision size: propose the small interview if it fits one agent session, or\n   Wayfinder if it needs more than one agent session. Ask the person to confirm\n   that route, or to skip vision entirely.\n\n## Found\n\nInitialize the local repository on its default branch, using the supplied\nplatform or Git configuration; ask if the branch cannot be established.\nMake the founding commit directly there with **only `README.md`, containing\nthe confirmed name and one-line purpose**. Verify the tree is clean.\n\nFor remote creation, use the hosting platform's own supplied authenticated\ntool with the confirmed namespace, name and visibility, then connect the local\nrepository and push the founding commit. Use an empty remote so it introduces\nno extra founding files. This step needs no repository-creation abstraction.\nWhen the tool or credential is absent, or local-only was chosen, finish this\nstep locally. Report the path and explain the later steps: create an empty\nremote with the intended namespace\u002Fvisibility, add its URL as a Git remote,\nthen push the default branch and any deliverable branches.\n\n## Adopt, when enabled\n\nFor remote GitHub project adoption, first have the owner establish the\nrepository-chosen exact check names in `.github\u002Frequired-checks.json` on the\ndestination default branch through the source's owner correction procedure.\nThis is a separate repository-policy change after the README-only founding\ncommit, outside the adoption commit and PR; adoption supplies neither this\nfile nor its names. If it is missing or invalid, stop before adoption, report\nthat owner action and retain the repository and interview answers for\ncontinuation. A local or proposed declaration cannot satisfy the trusted-default\nprerequisite. Local-only and workbench adoption keep their delivery below.\n\nIn the new repository, invoke `adopt-repository-standards` from the clean\ndefault branch after any prerequisite policy change. Pass a source only when\nthe person named one; otherwise keep that skill's Repo Canon default. Let\n`adopt` supply its profile descriptions\nand questions: standard for a repository no factory serves, factory only for\none served by a host-installed factory, workbench for a workbench. Add no\nsource or profile selector of your own. Pass the interview's license answer\ninto contextual work, resolving any remaining license requirement there.\n\nFollow the CLI's printed guidance. Once a run starts, use its pinned runtime\nfor completion and recovery. Before committing a completed run, preserve the\npinned runtime's `status --summary` output and `status` ready-to-commit verdict.\nDeliver one completed run per adoption PR under the new `CONTRIBUTING.md`:\nadoption branch, complete adoption record, separate review and squash merge.\nThe standard profile has no configured PR reviewer by default; follow its\ncontribution-guide delivery without imposing factory review-agent configuration.\nA workbench commits each completed adoption directly on its default branch.\n\nWhen the first remote project adoption installs the metadata workflow absent\nfrom default, carry its explicit owner-delivery stop through separate review,\nincluding on a private plan without protection or rulesets. Leave the PR open\nand stop with the exact reviewed head, saved pre-commit summary and verdict,\nvalidation outcomes, missing prerequisites, required owner action and next\nadoption continuation. Distinguish local validation from absent hosted checks.\nThis handoff grants no alternate merge authority: wait\u002Fmerge refusals stand,\nand owner delivery or correction must be confirmed before continuing below.\n\nFor local-only project adoption, commit the completed run on its adoption\nbranch and leave it ready to push and open its adoption PR once a remote exists. Report\nthat branch, saved pre-commit evidence, remaining review\u002Fmerge steps and the\nlater `adopt` continuation. The workbench direct-commit exception still applies.\nDo not try to open a remote PR locally. Retain this adopted tree for vision\nwork on a separate deliverable branch if needed.\n\nAfter remote adoption is delivered, return to the clean, updated default\nbranch and run `adopt` again without a source, as the source's remote-setup\ncontinuation directs. Inspect its actual selection: it may propose a newer\nCLI or standards release. This is a fresh full adoption run, not a promise of\nremote-settings-only work. Even an unchanged selection can write adoption\nbookkeeping; scope and contextual work are assessed again. Complete the run,\napply available remote setup or record the documented deferral, and preserve\nits pre-commit pinned summary and verdict before committing any changed files.\nDeliver those files as another adoption PR, or a direct workbench commit.\nA workbench installs no project remote setup; do not impose it there.\n\n## Vision and handoff\n\nRun the confirmed route in the new repository after creation\u002Fadoption:\n\n- **Small:** invoke `grill-with-docs`, composing `grilling` and `domain-modeling`.\n  Create domain documents only when the method warrants them. Before editing,\n  use an owned branch in an owned checkout; deliver under `CONTRIBUTING.md`.\n  Without that guide, leave edits on the method's own branch. For adopted\n  local-only work, leave the deliverable branch and report push\u002FPR steps and\n  its dependency on the pending adoption branch.\n- **Large:** invoke `wayfinder` in **chart the map** mode with the repository's\n  tracker. Use local-markdown for local-only work or when none is supplied.\n  Preserve Wayfinder's earlier no-fog stop when no map is warranted. Stop after\n  charting, including its research launches; report the map's name\u002Flink and how\n  to resume it with Wayfinder. Do not work through the map.\n- **Skip:** finish with the repository path and remaining work.\n\nAlways report local path, remote URL when created, delivered or pending branches\nand PRs, adoption\u002Fremote-setup deferrals and their continuation, and the vision\noutcome. Keep the founding, adoption and vision deliverables distinct.\n\n## Reads\n\nPaths are relative to the new repository root.\n\n- `README.md`: the founding name and purpose. When missing in the new empty\n  repository, create it for the founding commit.\n- `CONTRIBUTING.md`: adoption and domain-document delivery. When missing before\n  adoption, let adoption install it; without adoption, leave vision edits on\n  their own branch as `domain-modeling` directs.\n- `.github\u002Frequired-checks.json`: repository-owned check names for remote\n  GitHub project adoption. When missing or invalid, retain the created\n  repository and hand the separate default-branch policy change to the owner\n  before adoption; local-only and workbench delivery need no remote prerequisite.\n- The pinned CLI runtime and adoption state under `.repo-standards\u002F`, including\n  the `status --summary` adoption record: completion, recovery and pre-commit\n  evidence. When missing before adoption, let `adopt-repository-standards` start\n  the run; when a runtime needs restoring, follow the CLI's recovery guidance.\n- `docs\u002Fagents\u002Fissue-tracker.md`: the tracker for Wayfinder. When missing and\n  none is supplied, use local-markdown; local-only work always uses it.\n\nDependencies are installed skills, not files copied from another checkout:\n`adopt-repository-standards` only for adoption; `grill-with-docs`, `grilling` and\n`domain-modeling` for small vision; `wayfinder`, those small-route skills,\n`research` and `prototype` for large vision. Each method owns its further Reads\nand missing-input fallbacks. Hosting tools and tracker\u002Fsubagent capabilities\nare supplied by the session; honor each invoked command's standalone limits.\n","A prompt or brief naming this skill is its invocation.\n\nOwn the founding interview and creation. Delegate adoption to the separately\ninstalled `adopt-repository-standards` skill; delegate vision to `grill-with-docs`\nor `wayfinder`. Check the chosen route's dependencies before invoking it. The\nsmall route needs `grill-with-docs`, `grilling` and `domain-modeling`; Wayfinder\nalso needs `research` and `prototype`. If a required skill is missing, report\nits name and pause that step for installation, retaining the completed work.\n\n## Interview\n\nAsk one question at a time, proposing an answer from what the person has said\nand waiting for confirmation. Where there is no basis for a proposal, ask for\nthe value; invent no namespace, visibility, location or license. Reuse supplied\nanswers. If the interview shows the work belongs in an existing repository or\nneeds no repository, stop before creating anything.\n\nSettle these in order:\n\n1. Repository name and one-line purpose.\n2. Hosting namespace and visibility, unless the person chose local-only. If no\n   authenticated hosting-platform tool or credential is supplied, explain the\n   local fallback and skip remote questions that cannot be used.\n3. Parent directory. Resolve the proposed destination and check it and its\n   existing ancestors with Git, including linked worktrees and bare repositories.\n   Refuse a destination inside an existing Git work tree. Propose the current\n   directory as the parent only when it is outside every Git work tree, and\n   have the person confirm it. Use a new empty destination; preserve existing\n   content.\n4. License, including “none for now.” Keep the answer for adoption's contextual\n   work; this skill never chooses one or creates a license on the non-adoption\n   path.\n5. Whether to adopt repository standards. When invoked with adoption on (as\n   `create-adopted-repo` does), keep it on and skip this question.\n6. Vision size: propose the small interview if it fits one agent session, or\n   Wayfinder if it needs more than one agent session. Ask the person to confirm\n   that route, or to skip vision entirely.\n\n## Found\n\nInitialize the local repository on its default branch, using the supplied\nplatform or Git configuration; ask if the branch cannot be established.\nMake the founding commit directly there with **only `README.md`, containing\nthe confirmed name and one-line purpose**. Verify the tree is clean.\n\nFor remote creation, use the hosting platform's own supplied authenticated\ntool with the confirmed namespace, name and visibility, then connect the local\nrepository and push the founding commit. Use an empty remote so it introduces\nno extra founding files. This step needs no repository-creation abstraction.\nWhen the tool or credential is absent, or local-only was chosen, finish this\nstep locally. Report the path and explain the later steps: create an empty\nremote with the intended namespace\u002Fvisibility, add its URL as a Git remote,\nthen push the default branch and any deliverable branches.\n\n## Adopt, when enabled\n\nFor remote GitHub project adoption, first have the owner establish the\nrepository-chosen exact check names in `.github\u002Frequired-checks.json` on the\ndestination default branch through the source's owner correction procedure.\nThis is a separate repository-policy change after the README-only founding\ncommit, outside the adoption commit and PR; adoption supplies neither this\nfile nor its names. If it is missing or invalid, stop before adoption, report\nthat owner action and retain the repository and interview answers for\ncontinuation. A local or proposed declaration cannot satisfy the trusted-default\nprerequisite. Local-only and workbench adoption keep their delivery below.\n\nIn the new repository, invoke `adopt-repository-standards` from the clean\ndefault branch after any prerequisite policy change. Pass a source only when\nthe person named one; otherwise keep that skill's Repo Canon default. Let\n`adopt` supply its profile descriptions\nand questions: standard for a repository no factory serves, factory only for\none served by a host-installed factory, workbench for a workbench. Add no\nsource or profile selector of your own. Pass the interview's license answer\ninto contextual work, resolving any remaining license requirement there.\n\nFollow the CLI's printed guidance. Once a run starts, use its pinned runtime\nfor completion and recovery. Before committing a completed run, preserve the\npinned runtime's `status --summary` output and `status` ready-to-commit verdict.\nDeliver one completed run per adoption PR under the new `CONTRIBUTING.md`:\nadoption branch, complete adoption record, separate review and squash merge.\nThe standard profile has no configured PR reviewer by default; follow its\ncontribution-guide delivery without imposing factory review-agent configuration.\nA workbench commits each completed adoption directly on its default branch.\n\nWhen the first remote project adoption installs the metadata workflow absent\nfrom default, carry its explicit owner-delivery stop through separate review,\nincluding on a private plan without protection or rulesets. Leave the PR open\nand stop with the exact reviewed head, saved pre-commit summary and verdict,\nvalidation outcomes, missing prerequisites, required owner action and next\nadoption continuation. Distinguish local validation from absent hosted checks.\nThis handoff grants no alternate merge authority: wait\u002Fmerge refusals stand,\nand owner delivery or correction must be confirmed before continuing below.\n\nFor local-only project adoption, commit the completed run on its adoption\nbranch and leave it ready to push and open its adoption PR once a remote exists. Report\nthat branch, saved pre-commit evidence, remaining review\u002Fmerge steps and the\nlater `adopt` continuation. The workbench direct-commit exception still applies.\nDo not try to open a remote PR locally. Retain this adopted tree for vision\nwork on a separate deliverable branch if needed.\n\nAfter remote adoption is delivered, return to the clean, updated default\nbranch and run `adopt` again without a source, as the source's remote-setup\ncontinuation directs. Inspect its actual selection: it may propose a newer\nCLI or standards release. This is a fresh full adoption run, not a promise of\nremote-settings-only work. Even an unchanged selection can write adoption\nbookkeeping; scope and contextual work are assessed again. Complete the run,\napply available remote setup or record the documented deferral, and preserve\nits pre-commit pinned summary and verdict before committing any changed files.\nDeliver those files as another adoption PR, or a direct workbench commit.\nA workbench installs no project remote setup; do not impose it there.\n\n## Vision and handoff\n\nRun the confirmed route in the new repository after creation\u002Fadoption:\n\n- **Small:** invoke `grill-with-docs`, composing `grilling` and `domain-modeling`.\n  Create domain documents only when the method warrants them. Before editing,\n  use an owned branch in an owned checkout; deliver under `CONTRIBUTING.md`.\n  Without that guide, leave edits on the method's own branch. For adopted\n  local-only work, leave the deliverable branch and report push\u002FPR steps and\n  its dependency on the pending adoption branch.\n- **Large:** invoke `wayfinder` in **chart the map** mode with the repository's\n  tracker. Use local-markdown for local-only work or when none is supplied.\n  Preserve Wayfinder's earlier no-fog stop when no map is warranted. Stop after\n  charting, including its research launches; report the map's name\u002Flink and how\n  to resume it with Wayfinder. Do not work through the map.\n- **Skip:** finish with the repository path and remaining work.\n\nAlways report local path, remote URL when created, delivered or pending branches\nand PRs, adoption\u002Fremote-setup deferrals and their continuation, and the vision\noutcome. Keep the founding, adoption and vision deliverables distinct.\n\n## Reads\n\nPaths are relative to the new repository root.\n\n- `README.md`: the founding name and purpose. When missing in the new empty\n  repository, create it for the founding commit.\n- `CONTRIBUTING.md`: adoption and domain-document delivery. When missing before\n  adoption, let adoption install it; without adoption, leave vision edits on\n  their own branch as `domain-modeling` directs.\n- `.github\u002Frequired-checks.json`: repository-owned check names for remote\n  GitHub project adoption. When missing or invalid, retain the created\n  repository and hand the separate default-branch policy change to the owner\n  before adoption; local-only and workbench delivery need no remote prerequisite.\n- The pinned CLI runtime and adoption state under `.repo-standards\u002F`, including\n  the `status --summary` adoption record: completion, recovery and pre-commit\n  evidence. When missing before adoption, let `adopt-repository-standards` start\n  the run; when a runtime needs restoring, follow the CLI's recovery guidance.\n- `docs\u002Fagents\u002Fissue-tracker.md`: the tracker for Wayfinder. When missing and\n  none is supplied, use local-markdown; local-only work always uses it.\n\nDependencies are installed skills, not files copied from another checkout:\n`adopt-repository-standards` only for adoption; `grill-with-docs`, `grilling` and\n`domain-modeling` for small vision; `wayfinder`, those small-route skills,\n`research` and `prototype` for large vision. Each method owns its further Reads\nand missing-input fallbacks. Hosting tools and tracker\u002Fsubagent capabilities\nare supplied by the session; honor each invoked command's standalone limits.\n",{"name":5,"description":7,"disable-model-invocation":20},"main","f5a3e334f7bc0fce1854f224a8e78c53f8ea75b9",".agents\u002Fskills\u002Fcreate-repository",0,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon","https:\u002F\u002Frepo-standards.com\u002Fsources\u002Flutzseverino\u002Frepo-canon\u002F","https:\u002F\u002Fgithub.com\u002Flutzseverino","If Codex could write profile bios, you wouldn't be reading this. Or would you?","2026-11-15 06:12:31",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lutzseverino\u002Frepo-canon --skill create-repository",{"tool":39,"command":40},"bunx","bunx skills add lutzseverino\u002Frepo-canon --skill create-repository",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lutzseverino\u002Frepo-canon --skill create-repository","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-repository\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",42,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-repository\u002Fagents\u002Fopenai.yaml",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"CREDITS.md",99,"https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcreate-repository\u002FCREDITS.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CP829W88YVACQ3ZFS4KYAK","repository-standards","Look up installed rules before any work in a disposable planning exercise, including tracker work and file changes.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002Fscripts\u002Fsupport\u002Frepository-standards\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CP7Y70KNBJBVDNGSQ6RGG4","triage","Move issues and external PRs through a state machine of triage roles, sort each request by where its uncertainty lies, and bring its agent brief to acceptance through research and independent review, or through a grilling session with the owner.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CP7TWX07ST84HT5XNEYS1J","orchestrate","Turn the owner's feature or problem into an approved plan across tickets, keep its state in the workbench, and run it to an announced close.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Forchestrate\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CP7QE6M9W0E24BV0VZV1RS","babysit","Babysit an opened pull request through checks and review to merge or its prescribed handoff. Use right after opening a pull request, or when asked to babysit or land one.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.repo-standards\u002Finputs\u002Fsource\u002F.agents\u002Fskills\u002Fbabysit\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CP7N4VMT6C4THVN2RBRB5Q","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7CP7GN4YYS18YS91N0AN0PK","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flutzseverino\u002Frepo-canon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]