[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C44SW6JFF3946GAV7CKJYH":3,"skill-same:01M6C44SW6JFF3946GAV7CKJYH":70},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":69},"01M6C44SW6JFF3946GAV7CKJYH","onboard-team",null,"Take a new or half-set-up delivery team to a working state with the person — its team, members, board, repositories, team page and charter, dispatch, and local wiring. Reads first, lists the gaps, asks before each write; safe to run again.","colliery-io\u002Fkairos","colliery-io","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F167646339?v=4","01M6C4368BHZH1AYSJ3SX124ET","Colliery","01M6C436CSYPJ80ZNK1SA2Q7Z3",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fworkflow\u002Fonboard-team\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"team","onboard","onboard team","up","new","repositories","gaps","charter","wiring","true","with","name","local","delivery","safe","dispatch","write","board","page","first","SET","state","run","2026-11-10 10:12:30",false,"---\nname: onboard-team\ndescription: Take a new or half-set-up delivery team to a working state with the person — its team, members, board, repositories, team page and charter, dispatch, and local wiring. Reads first, lists the gaps, asks before each write; safe to run again.\nargument-hint: \"[team slug | new team name]\"\ndisable-model-invocation: true\n---\n\n# Onboard a team\n\nTake one delivery team to a working state, step by step, with the person. Do this when a team is new, or when a team works but has gaps: no repository linked, an empty charter, no route for requests.\n\nThe rules:\n\n- **Read first.** Read the state of the team before you write. Then show the person a checklist of what is there and what is missing.\n- **Ask before each write.** Say what you will change, and wait for a yes. A \"yes\" to one step is not a yes to the next.\n- **Only fix what is missing.** You can run this skill again on a team that is set up. Do not change a thing that is already correct.\n- **Use the MCP tools.** When a step has no MCP tool, use the CLI command that this skill names, or tell the person which step they must do in the web UI.\n\n## 0. Check the admin tools\n\nMost tools of this skill are in the admin profile of the Kairos MCP server (KAIROS-T-0454): `create_team`, `update_team`, `add_team_member`, `grant_capability`, the column and transition tools, the dispatch tools, `set_agent_triage` and the tools that write the team page. The default server (`\u002Fmcp`) does not list them, and Claude Code calls only the tools that a server lists.\n\nLook for the `kairos-admin` server: its tools have names such as `mcp__kairos-admin__create_team_page`. (`team_pages`, which reads the team page, and `list_dispatch_rules` are on the default server only: read with the default server, write with `kairos-admin`.) If it is not there, tell the person to add it with this command, then to start a new session:\n\n```sh\nclaude mcp add --scope user kairos-admin -- kairos mcp-proxy --profile admin\n```\n\nThe command adds a second `kairos mcp-proxy` with the admin profile. It uses the same deployment and credential as the `kairos` server of the plugin: `kairos login`, or an agent key in `KAIROS_KEY` or `KAIROS_MCP_KEY`. Do not add the server yourself, and do not add a different MCP server: the person decides.\n\nUse the `kairos-admin` tools for the admin steps, and the default server for the rest.\n\n**The CLI fallback.** When the person does not add the server, use the CLI for the admin steps. It uses the same login. For example:\n\n- A team and its delivery board: `kairos teams create --name \u003CNAME> --slug \u003CSLUG> --code-prefix \u003CPREFIX> [--kind \u003CKIND>]`.\n- Members: `kairos teams members add|remove`.\n- Boards, columns and transitions: `kairos boards --help`.\n- The team page: `kairos teams pages list|show|create|edit|move|delete`.\n\nRun `kairos \u003Ccommand> --help` for the arguments. Show the person each command before you run it.\n\n## 1. Read the state\n\nFind the team with `whoami` (your teams) and `my_boards` (boards, columns, the team of each ADR board). For a team that does not exist yet, go to step 2.\n\nCollect:\n\n| Part | Read with |\n|---|---|\n| The team: name, slug, type | `whoami`, `my_boards` |\n| Members | `kairos teams members list \u003CTEAM>` (slug or UUID; no MCP tool reads members) |\n| Delivery board: prefix, columns, entry column, WIP limits | `my_boards`; `kairos boards show \u003CBOARD>` |\n| Transitions | `kairos boards transitions list \u003CBOARD>` (no MCP tool reads them) |\n| ADR board | `my_boards` (`ADR board of the team \u003Cslug>`) |\n| Repositories, each with one owner team | `list_repositories {team}`, `get_repository` |\n| Team page: the charter and the tree | `team_pages {team}`, then `team_pages {team, page: \"charter\"}` |\n| Dispatch rules of the board | `list_dispatch_rules {board}` |\n\nThen show the checklist. Mark each line **ok**, **missing** or **to check**. Example:\n\n```text\nTeam platform — checklist\n  ok       team, stream_aligned, 4 members\n  ok       delivery board platform-delivery (PLAT), entry column Backlog\n  to check ADR board: none (does the team record its own decisions?)\n  missing  repository payments-api has no owner team here\n  missing  charter: still the empty skeleton\n  to check dispatch: no rules (does the team use a board session?)\n```\n\nAsk the person which lines to work on, in which order.\n\n## 2. The team and its members\n\n- **No team:** `create_team {name, slug, code_prefix}`. It makes the team and its delivery board (`{slug}-delivery`); an ADR board is a question of step 3. The prefix does not change later, so agree it with the person first.\n- **A different name or type:** `update_team`.\n- **Members:** `add_team_member {team, user}` for each person. Membership gives `manage_tasks`, `manage_documents` and `transition_items` on the boards of the team, and the right to edit the team page. `remove_team_member` takes a person off.\n- **An agent of the team** (a service account or the agent key of a person) must also be a member to edit the team page. A board capability does not give that right.\n- **Extra rights:** `grant_capability` or `set_board_capabilities`, for example `configure_boards` for the person who looks after the board.\n\nThese calls need the organization admin role or `manage_structure` on the organization. If they are refused, tell the person who can do them.\n\n## 3. The board\n\nThe delivery board gets the default columns and transitions. Change them only when the team works in a different way.\n\n- **Columns:** `add_column`, `update_column` (name, position, WIP limit, done column), `remove_column`.\n- **Transitions:** `set_transition`. A board allows one-column hops by default.\n- **No ADR board, and the team wants one:** `create_board {board_level: \"adr\", team, ...}` with the prefix of the team.\n\n## 4. Repositories\n\nEach repository has exactly one owner team. For each repository of the team:\n\n- Not in the directory: `add_repository` with the team as owner.\n- In the directory with a different owner: ask the person. A move to this team is `update_repository` with `team`, or `kairos repos update --team`. You need the right on the old team and on the new team.\n- The description says how to work in the repository (build, test, review). Fill it in with `update_repository` when it is empty.\n\n## 5. The team page\n\nThe team page has the charter and the folders and pages that the team grows. A folder holds folders and pages. A page holds nothing. You need membership of the team (or the organization admin role) to write.\n\n**The charter** is the landing page and the social contract of the team. Write it with the person, not for them. Ask one question at a time and put the answers in these sections:\n\n- **Mission:** why the team exists, in one or two sentences.\n- **Scope:** what the team owns (products, repositories, services) and what it does not.\n- **How to send us work:** a request to this team is a task on its delivery board. It lands in the entry column, in the support lane. Name who triages, and how often.\n- **Ways of working:** the cadence, reviews, on-call, where decisions are recorded.\n- **Success measures:** how the team knows it is doing well.\n\nRead the charter first (`team_pages {team, page: \"charter\"}`), and keep what the person already wrote. Save it with `edit_team_page {team, page: \"charter\", content, version}`. Use the version that you read. A `CONFLICT` means that somebody saved first: read again, merge, and save.\n\n**Folders and pages:** there is no fixed set. Ask the person what the team writes down (runbooks, how-to guides, design documents), and make only those: `create_team_page {team, kind: \"folder\", title}`, then pages in them with `parent`. `move_team_page` moves, reorders or renames. `delete_team_page` archives a page, or a folder with everything in it; a person restores it in the Archived list of the Pages view of the team.\n\nThe same steps are in the CLI: `kairos teams pages list|show|create|edit|move|delete`.\n\n## 6. Dispatch and agent triage (when the team uses a board session)\n\nAsk the person whether an agent session works the board of the team. If no, skip this step. If yes:\n\n- Check `list_dispatch_rules {board}`. It also shows the agent triage setting. A missing rule: `create_dispatch_rule` (it can make the webhook target from `url`).\n- Ask who decides the triage of intake (a request in the support lane). By default a person decides, and an agent only writes its proposal with `append_note`. When the team wants the agent to decide, call `set_agent_triage {board, agents_decide: true}`. It needs `configure_boards` on the board.\n\n## 7. Local wiring\n\nIn each checkout of a repository of the team, run `\u002Fkairos:bootstrap`. It adds a `[[project]]` with the team board and the repository to `config.toml` of the user (`kairos config project`). The repository gets no file. Then check that the repository has a code index: `rebuild_code_index` builds one when it is missing.\n\n## 8. Close\n\nRead the state again (step 1) and show the checklist. Each line must be **ok**, or the person must agree that it stays open. For each line that stays open, give the reason and who can close it.\n","# Onboard a team\n\nTake one delivery team to a working state, step by step, with the person. Do this when a team is new, or when a team works but has gaps: no repository linked, an empty charter, no route for requests.\n\nThe rules:\n\n- **Read first.** Read the state of the team before you write. Then show the person a checklist of what is there and what is missing.\n- **Ask before each write.** Say what you will change, and wait for a yes. A \"yes\" to one step is not a yes to the next.\n- **Only fix what is missing.** You can run this skill again on a team that is set up. Do not change a thing that is already correct.\n- **Use the MCP tools.** When a step has no MCP tool, use the CLI command that this skill names, or tell the person which step they must do in the web UI.\n\n## 0. Check the admin tools\n\nMost tools of this skill are in the admin profile of the Kairos MCP server (KAIROS-T-0454): `create_team`, `update_team`, `add_team_member`, `grant_capability`, the column and transition tools, the dispatch tools, `set_agent_triage` and the tools that write the team page. The default server (`\u002Fmcp`) does not list them, and Claude Code calls only the tools that a server lists.\n\nLook for the `kairos-admin` server: its tools have names such as `mcp__kairos-admin__create_team_page`. (`team_pages`, which reads the team page, and `list_dispatch_rules` are on the default server only: read with the default server, write with `kairos-admin`.) If it is not there, tell the person to add it with this command, then to start a new session:\n\n```sh\nclaude mcp add --scope user kairos-admin -- kairos mcp-proxy --profile admin\n```\n\nThe command adds a second `kairos mcp-proxy` with the admin profile. It uses the same deployment and credential as the `kairos` server of the plugin: `kairos login`, or an agent key in `KAIROS_KEY` or `KAIROS_MCP_KEY`. Do not add the server yourself, and do not add a different MCP server: the person decides.\n\nUse the `kairos-admin` tools for the admin steps, and the default server for the rest.\n\n**The CLI fallback.** When the person does not add the server, use the CLI for the admin steps. It uses the same login. For example:\n\n- A team and its delivery board: `kairos teams create --name \u003CNAME> --slug \u003CSLUG> --code-prefix \u003CPREFIX> [--kind \u003CKIND>]`.\n- Members: `kairos teams members add|remove`.\n- Boards, columns and transitions: `kairos boards --help`.\n- The team page: `kairos teams pages list|show|create|edit|move|delete`.\n\nRun `kairos \u003Ccommand> --help` for the arguments. Show the person each command before you run it.\n\n## 1. Read the state\n\nFind the team with `whoami` (your teams) and `my_boards` (boards, columns, the team of each ADR board). For a team that does not exist yet, go to step 2.\n\nCollect:\n\n| Part | Read with |\n|---|---|\n| The team: name, slug, type | `whoami`, `my_boards` |\n| Members | `kairos teams members list \u003CTEAM>` (slug or UUID; no MCP tool reads members) |\n| Delivery board: prefix, columns, entry column, WIP limits | `my_boards`; `kairos boards show \u003CBOARD>` |\n| Transitions | `kairos boards transitions list \u003CBOARD>` (no MCP tool reads them) |\n| ADR board | `my_boards` (`ADR board of the team \u003Cslug>`) |\n| Repositories, each with one owner team | `list_repositories {team}`, `get_repository` |\n| Team page: the charter and the tree | `team_pages {team}`, then `team_pages {team, page: \"charter\"}` |\n| Dispatch rules of the board | `list_dispatch_rules {board}` |\n\nThen show the checklist. Mark each line **ok**, **missing** or **to check**. Example:\n\n```text\nTeam platform — checklist\n  ok       team, stream_aligned, 4 members\n  ok       delivery board platform-delivery (PLAT), entry column Backlog\n  to check ADR board: none (does the team record its own decisions?)\n  missing  repository payments-api has no owner team here\n  missing  charter: still the empty skeleton\n  to check dispatch: no rules (does the team use a board session?)\n```\n\nAsk the person which lines to work on, in which order.\n\n## 2. The team and its members\n\n- **No team:** `create_team {name, slug, code_prefix}`. It makes the team and its delivery board (`{slug}-delivery`); an ADR board is a question of step 3. The prefix does not change later, so agree it with the person first.\n- **A different name or type:** `update_team`.\n- **Members:** `add_team_member {team, user}` for each person. Membership gives `manage_tasks`, `manage_documents` and `transition_items` on the boards of the team, and the right to edit the team page. `remove_team_member` takes a person off.\n- **An agent of the team** (a service account or the agent key of a person) must also be a member to edit the team page. A board capability does not give that right.\n- **Extra rights:** `grant_capability` or `set_board_capabilities`, for example `configure_boards` for the person who looks after the board.\n\nThese calls need the organization admin role or `manage_structure` on the organization. If they are refused, tell the person who can do them.\n\n## 3. The board\n\nThe delivery board gets the default columns and transitions. Change them only when the team works in a different way.\n\n- **Columns:** `add_column`, `update_column` (name, position, WIP limit, done column), `remove_column`.\n- **Transitions:** `set_transition`. A board allows one-column hops by default.\n- **No ADR board, and the team wants one:** `create_board {board_level: \"adr\", team, ...}` with the prefix of the team.\n\n## 4. Repositories\n\nEach repository has exactly one owner team. For each repository of the team:\n\n- Not in the directory: `add_repository` with the team as owner.\n- In the directory with a different owner: ask the person. A move to this team is `update_repository` with `team`, or `kairos repos update --team`. You need the right on the old team and on the new team.\n- The description says how to work in the repository (build, test, review). Fill it in with `update_repository` when it is empty.\n\n## 5. The team page\n\nThe team page has the charter and the folders and pages that the team grows. A folder holds folders and pages. A page holds nothing. You need membership of the team (or the organization admin role) to write.\n\n**The charter** is the landing page and the social contract of the team. Write it with the person, not for them. Ask one question at a time and put the answers in these sections:\n\n- **Mission:** why the team exists, in one or two sentences.\n- **Scope:** what the team owns (products, repositories, services) and what it does not.\n- **How to send us work:** a request to this team is a task on its delivery board. It lands in the entry column, in the support lane. Name who triages, and how often.\n- **Ways of working:** the cadence, reviews, on-call, where decisions are recorded.\n- **Success measures:** how the team knows it is doing well.\n\nRead the charter first (`team_pages {team, page: \"charter\"}`), and keep what the person already wrote. Save it with `edit_team_page {team, page: \"charter\", content, version}`. Use the version that you read. A `CONFLICT` means that somebody saved first: read again, merge, and save.\n\n**Folders and pages:** there is no fixed set. Ask the person what the team writes down (runbooks, how-to guides, design documents), and make only those: `create_team_page {team, kind: \"folder\", title}`, then pages in them with `parent`. `move_team_page` moves, reorders or renames. `delete_team_page` archives a page, or a folder with everything in it; a person restores it in the Archived list of the Pages view of the team.\n\nThe same steps are in the CLI: `kairos teams pages list|show|create|edit|move|delete`.\n\n## 6. Dispatch and agent triage (when the team uses a board session)\n\nAsk the person whether an agent session works the board of the team. If no, skip this step. If yes:\n\n- Check `list_dispatch_rules {board}`. It also shows the agent triage setting. A missing rule: `create_dispatch_rule` (it can make the webhook target from `url`).\n- Ask who decides the triage of intake (a request in the support lane). By default a person decides, and an agent only writes its proposal with `append_note`. When the team wants the agent to decide, call `set_agent_triage {board, agents_decide: true}`. It needs `configure_boards` on the board.\n\n## 7. Local wiring\n\nIn each checkout of a repository of the team, run `\u002Fkairos:bootstrap`. It adds a `[[project]]` with the team board and the repository to `config.toml` of the user (`kairos config project`). The repository gets no file. Then check that the repository has a code index: `rebuild_code_index` builds one when it is missing.\n\n## 8. Close\n\nRead the state again (step 1) and show the checklist. Each line must be **ok**, or the person must agree that it stays open. For each line that stays open, give the reason and who can close it.\n",{"name":5,"description":7,"argument-hint":47,"disable-model-invocation":48},"[team slug | new team name]",true,"main","f8e176327eded0a5699a22509fbf8a8338cbffc6","plugin\u002Fskills\u002Fworkflow\u002Fonboard-team",4,"https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos","https:\u002F\u002Fgithub.com\u002Fcolliery-io","https:\u002F\u002Fcolliery.io\u002F","2026-11-13 02:51:01",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":48},[59,62,65],{"tool":60,"command":61},"npx","npx skills add colliery-io\u002Fkairos --skill onboard-team",{"tool":63,"command":64},"bunx","bunx skills add colliery-io\u002Fkairos --skill onboard-team",{"tool":66,"command":67},"pnpm","pnpm dlx skills add colliery-io\u002Fkairos --skill onboard-team","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fworkflow\u002Fonboard-team\u002FSKILL.md",[],[71,94,108,122,133,147],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":42},"01M6C4534Y6DB5N1V03Q5N9HVG","triage","Groom the delivery board — refine acceptance criteria, prioritize bugs, weigh tech debt, archive stale items, restock Todo, escalate cross-team blockers.","https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fworkflow\u002Ftriage\u002FSKILL.md",[],[73,78,28,79,80,19,81,82,83,84,85,86,87,88,36,89,90,91,92,32,93],"refine","stale","debt","restock","groom","tech","bugs","acceptance criteria","todo","archive","short","code","acceptance","prioritize","tech debt","escalate",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":42},"01M6C450QYKWYHEA0VHZCM5XEW","to-initiative","Turn the current conversation into a Kairos initiative with an attached PRD — no interview, just synthesis of what's already been discussed.","https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fworkflow\u002Fto-initiative\u002FSKILL.md",[],[101,102,103,104,105,106,29,107,28],"to initiative","prd","just","kairos","interview","conversation","Synthesis",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":42},"01M6C44YQG7CESHVHC6Z0TADZC","ralph","Run Kairos tasks one by one in a Ralph loop, through the steps of \u002Fkairos:implement.","https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fworkflow\u002Fralph\u002FSKILL.md",[],[110,28,115,116,117,88,118,119,89,41,120,121,104],"ralph loop","task","max","implement","tasks","loop","max-iterations",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":42},"01M6C44WW9QWDTG173VFRA7E1Y","ralph-initiative","Run the open tasks of a Kairos initiative in a Ralph loop, in the sequence of their blocks edges.","https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fworkflow\u002Fralph-initiative\u002FSKILL.md",[],[129,110,41,115,28,130,131,117,88,119,89,120,104,121,132],"ralph initiative","blocks","sequence","open",{"skillNo":134,"name":118,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":42},"01M6C44QPDV3F8F6JC9B2NEDNX","Implement one Kairos task from Todo to Completed. Use when the user names a task or short code to implement, asks to pick up the next todo item, or when groomed work is handed off for execution.","https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fworkflow\u002Fimplement\u002FSKILL.md",[],[118,89,139,104,140,22,141,88,142,143,116,144,145,146,86],"use","execution","pick","work","user","when","for","next",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":42},"01M6C44MV0QTRBA8JB8W99KCPS","grill-initiative","A relentless interview that sharpens a Kairos initiative (or a strategy) and writes each settled answer into the item at once. Pass an initiative or strategy short code, or a title for a new initiative.","https:\u002F\u002Fgithub.com\u002Fcolliery-io\u002Fkairos\u002Fblob\u002Fmain\u002Fplugin\u002Fskills\u002Fworkflow\u002Fgrill-initiative\u002FSKILL.md",[],[154,155,28,23,156,157,145,158,88,89,104,159,105],"grill initiative","grill","at","answer","title","strategy"]