[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EF1K3JY985JR0SNTSSV6SB":3,"skill-same:01M7EF1K3JY985JR0SNTSSV6SB":45},{"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":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7EF1K3JY985JR0SNTSSV6SB","orchestration",null,"Use Orca orchestration for structured multi-agent coordination: threaded messages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation waits, task DAGs, decision gates, coordinator loops, or decomposing work across agents. Use `orca-cli` instead for full ownership handoffs, including requests phrased as \"hand off\", \"handoff\", \"handover\", \"give this to another agent\", or \"another worktree\" when the user did not explicitly ask to supervise, monitor, wait for results, or coordinate a DAG. Use `orca-cli` for ordinary terminal control, lightweight terminal prompts, shell commands, Orca worktree management, reading or waiting on terminals, and automation of the browser embedded inside Orca. Use Computer Use for browser windows, webviews, Orca app UI, or desktop UI outside Orca's embedded browser.","vladborsh\u002Fcityplanner","vladborsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11244920?v=4","01M7EF0R90THK54J298DMGSY6D","Vlad Borsh","01M7EF0R9JWXP5WTYFG0XADXVZ",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Forchestration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: orchestration\ndescription: >-\n  Use Orca orchestration for structured multi-agent coordination: threaded\n  messages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation\n  waits, task DAGs, decision gates, coordinator loops, or decomposing work\n  across agents. Use `orca-cli` instead for full ownership handoffs, including\n  requests phrased as \"hand off\", \"handoff\", \"handover\", \"give this to another\n  agent\", or \"another worktree\" when the user did not explicitly ask to\n  supervise, monitor, wait for results, or coordinate a DAG. Use `orca-cli` for\n  ordinary terminal control, lightweight terminal prompts, shell commands, Orca\n  worktree management, reading or waiting on terminals, and automation of the\n  browser embedded inside Orca. Use Computer Use for browser windows, webviews,\n  Orca app UI, or desktop UI outside Orca's embedded browser.\n---\n\n# Orca Orchestration\n\nThis file is a discovery stub, not the usage guide. The full, version-matched Orca\norchestration reference is served by the `orca` binary itself — kept out of this file on\npurpose so it can never drift from the binary that will actually run your commands.\n\nEngage Orca orchestration whenever you need structured multi-agent coordination: threaded\nmessages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation waits, task DAGs,\ndecision gates, coordinator loops, or decomposing work across agents. Use the orca-cli skill\ninstead for full ownership handoffs (\"hand off\", \"handoff\", \"handover\", \"give this to\nanother agent\", \"another worktree\") when the user did not ask to supervise, monitor, wait\nfor results, or coordinate a DAG — and for ordinary terminal control, shell commands,\nworktree management, and the built-in browser. Coordination requires real Orca runtime\nstate; never substitute a non-Orca subagent tool.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n  for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n  `orca` there — outside Orca's terminals it normally resolves to the\n  GNOME Orca screen reader (`\u002Fusr\u002Fbin\u002Forca`) and starts speech on the user's machine.\n- Otherwise, use `orca`.\n\nBelow, `ORCA` is a placeholder for the executable you resolved. Substitute it before\nrunning anything; do not create a shell variable or run `ORCA` literally. This works the\nsame way in POSIX shells, PowerShell, and cmd.exe.\n\nIf the selected executable cannot run, report its exact error and stop. Do not fall through\nto another executable, which could silently target a different Orca build.\n\n## Load the full guide before running Orca commands\n\n```text\nORCA skills get orchestration\n```\n\nThat prints the complete, version-matched guide for the exact binary that will handle your\nnext commands — task creation and dispatch, injected lifecycle preambles, worker_done\nauthority, decision gates, and coordinator loops. Read it first, then run the specific\ncommand you need.\n\nDon't guess subcommands or flags from memory or from a cached copy of this stub. They\nchange between Orca releases, and this file deliberately no longer lists them. Confirm the\napp is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and\nprefer `--json` for agent-driven calls.\n\n## If an older Orca does not recognize `skills get`\n\nUse this fallback only when the selected binary explicitly reports that `skills get` is an\nunknown command. Another failure is not proof of an older binary; report it rather than\nguessing or changing executables. For a confirmed pre-guide binary, use only this bounded,\nread-only bootstrap to orient. Do not dead-end and do not invent commands:\n\n```text\nORCA status --json\nORCA orchestration task-list --json\nORCA terminal list --json\n```\n\nThen tell the user that updating Orca restores the full, version-matched guide via\n`ORCA skills get orchestration`. Beyond these commands, ask the user rather than guessing a\ncommand surface this older binary may not support.\n","# Orca Orchestration\n\nThis file is a discovery stub, not the usage guide. The full, version-matched Orca\norchestration reference is served by the `orca` binary itself — kept out of this file on\npurpose so it can never drift from the binary that will actually run your commands.\n\nEngage Orca orchestration whenever you need structured multi-agent coordination: threaded\nmessages, blocking ask\u002Freply flows, task dispatch, worker_done\u002Fescalation waits, task DAGs,\ndecision gates, coordinator loops, or decomposing work across agents. Use the orca-cli skill\ninstead for full ownership handoffs (\"hand off\", \"handoff\", \"handover\", \"give this to\nanother agent\", \"another worktree\") when the user did not ask to supervise, monitor, wait\nfor results, or coordinate a DAG — and for ordinary terminal control, shell commands,\nworktree management, and the built-in browser. Coordination requires real Orca runtime\nstate; never substitute a non-Orca subagent tool.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n  for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n  `orca` there — outside Orca's terminals it normally resolves to the\n  GNOME Orca screen reader (`\u002Fusr\u002Fbin\u002Forca`) and starts speech on the user's machine.\n- Otherwise, use `orca`.\n\nBelow, `ORCA` is a placeholder for the executable you resolved. Substitute it before\nrunning anything; do not create a shell variable or run `ORCA` literally. This works the\nsame way in POSIX shells, PowerShell, and cmd.exe.\n\nIf the selected executable cannot run, report its exact error and stop. Do not fall through\nto another executable, which could silently target a different Orca build.\n\n## Load the full guide before running Orca commands\n\n```text\nORCA skills get orchestration\n```\n\nThat prints the complete, version-matched guide for the exact binary that will handle your\nnext commands — task creation and dispatch, injected lifecycle preambles, worker_done\nauthority, decision gates, and coordinator loops. Read it first, then run the specific\ncommand you need.\n\nDon't guess subcommands or flags from memory or from a cached copy of this stub. They\nchange between Orca releases, and this file deliberately no longer lists them. Confirm the\napp is up with `ORCA status --json` (start it with `ORCA open --json` if needed), and\nprefer `--json` for agent-driven calls.\n\n## If an older Orca does not recognize `skills get`\n\nUse this fallback only when the selected binary explicitly reports that `skills get` is an\nunknown command. Another failure is not proof of an older binary; report it rather than\nguessing or changing executables. For a confirmed pre-guide binary, use only this bounded,\nread-only bootstrap to orient. Do not dead-end and do not invent commands:\n\n```text\nORCA status --json\nORCA orchestration task-list --json\nORCA terminal list --json\n```\n\nThen tell the user that updating Orca restores the full, version-matched guide via\n`ORCA skills get orchestration`. Beyond these commands, ask the user rather than guessing a\ncommand surface this older binary may not support.\n",{"name":5,"description":7},"master","25fc666e7380e9f3db2eecaba93538cf788db974","agents\u002Fclaude-skills\u002Forchestration","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner","https:\u002F\u002Fgithub.com\u002Fvladborsh","turn ideas into software applications","2026-10-30 17:49:55",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add vladborsh\u002Fcityplanner --skill orchestration",{"tool":37,"command":38},"bunx","bunx skills add vladborsh\u002Fcityplanner --skill orchestration",{"tool":40,"command":41},"pnpm","pnpm dlx skills add vladborsh\u002Fcityplanner --skill orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Forchestration\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M7EF1V091775NVRCXB0V8J7A","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fwait-what\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7EF1S6M2Y11XKAJ0WBTMAH1","to-questionnaire","Turn a decision you can't fully answer into a questionnaire for someone else to fill in.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fto-questionnaire\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7EF1D1XD6AXY0Z4G9G87SJH","orca-cli","Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and the browser embedded inside the Orca app. Use when the user says \"$orca-cli\", \"use orca cli\", \"Orca worktree\", \"child worktree\", \"cardStatus\", \"spawn codex\u002Fclaude in a worktree\", \"read\u002Fwait\u002Fsend Orca terminal\", \"terminal send\", \"full handoff\", \"handover\", \"give this to another agent\", \"another worktree\", \"Orca browser\", \"orca artifacts\", \"share HTML\u002FMarkdown\", \"public artifact link\", \"share skills\", or \"control the browser inside Orca\". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Orca-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Orca's embedded browser.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Forca-cli\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7EF1BAWXJG8QP95MH9RPKZ8","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7EF18D2T2RW1QG30JWCTZYV","grill-with-docs","A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fgrill-with-docs\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7EF179QETSAQ8QZ2R4J880S","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002Fvladborsh\u002Fcityplanner\u002Fblob\u002Fmaster\u002Fagents\u002Fclaude-skills\u002Fgrill-me\u002FSKILL.md",[],[]]