[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73A1W2SW7B11MA8S82ZNM8S":3,"skill-same:01M73A1W2SW7B11MA8S82ZNM8S":47},{"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":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M73A1W2SW7B11MA8S82ZNM8S","sentinel-protocol",null,"Core Kairon completion-signalling protocol. Defines the sentinel file path format and write rules that every pipeline agent uses to signal task completion to krew-lead, and that krew-lead uses to detect it. This is engine behavior, not a project convention — do not override it per project.","jbrinkman\u002Fkairon","jbrinkman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F862921?v=4","01M73A1DTKY13WY1KRJ4QETJ2F","Joe Brinkman","01M73A1DV9EYRCCSSRFCYXYXMJ",3,"MIT","https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fsentinel-protocol\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: sentinel-protocol\ndescription: Core Kairon completion-signalling protocol. Defines the sentinel file path format and write rules that every pipeline agent uses to signal task completion to krew-lead, and that krew-lead uses to detect it. This is engine behavior, not a project convention — do not override it per project.\n---\n\n# Sentinel Protocol\n\nKairon detects agent\u002Ftask completion via **sentinel files** written to\n`.kairon\u002Fartifacts\u002F`, using a naming convention (NOT via agent JSON config\nfields). This skill is the single source of truth for that path format and the\nwrite rules. Every pipeline agent (architect, builder, validator, documenter)\nwrites a sentinel; krew-lead reads it. All of them reference this skill so the\nconvention is defined once.\n\n## Path Format\n\nPlan-based tasks (a task has an `id`):\n\n```\n.kairon\u002Fartifacts\u002F\u003Cagent>-\u003Cissue-number>-\u003Ctask-id>.md\n```\n\n- `\u003Cagent>` — the writing agent's name (e.g. `builder`, `validator`).\n- `\u003Cissue-number>` — the GitHub issue number being processed.\n- `\u003Ctask-id>` — the plan task's `id` field (unique per plan).\n\nIncluding `\u003Ctask-id>` is required: a single plan can assign several tasks to\nthe **same** agent (e.g. two `builder` tasks). Without the task id those tasks\nwould write and read the **same** file, so a later task could overwrite an\nearlier task's sentinel, or a completion check could misread a stale sentinel\nfrom a previous task as the current task's success.\n\n### Legacy \u002F non-plan fallback\n\nWhen there is no plan and therefore no task id (the legacy sequential\nworkflow), and for whole-issue signals that are not tied to a specific plan\ntask, use the task-less form:\n\n```\n.kairon\u002Fartifacts\u002F\u003Cagent>-\u003Cissue-number>.md\n```\n\nA reader that expects a plan task MUST use the `\u003Ctask-id>` form and MUST NOT\nfall back to the task-less form to satisfy a task-scoped check (that is exactly\nthe stale-read this protocol prevents).\n\n## Write Rules (writing agents)\n\n1. After completing your work, write your sentinel at the path above for your\n   agent name, the current issue number, and — for a plan task — the task id.\n2. Write to that path only. Do not write sentinels for other agents or tasks.\n3. Include a brief summary of what you produced so krew-lead can recover your\n   result from the file if your response is otherwise empty.\n4. A sentinel's presence with a success summary signals successful completion.\n5. If you could not deliver all of your assigned work, write the sentinel with\n   `**Status**: BLOCKED`, quote each item you could not deliver, and say why.\n   Never write a success summary for partial work. krew-lead treats BLOCKED as\n   a failure and escalates it to a human.\n\n## Read Rules (krew-lead)\n\n1. A plan task is complete only when its task-scoped sentinel\n   (`\u003Cagent>-\u003Cissue-number>-\u003Ctask-id>.md`) exists with a success status.\n2. On an empty subagent response, check for the sentinel before retrying:\n   `test -f .kairon\u002Fartifacts\u002F\u003Cagent>-\u003Cissue-number>-\u003Ctask-id>.md`; if it\n   exists, read it to recover the summary and continue; if missing, proceed\n   with normal retry escalation.\n3. Never accept a task-less sentinel as proof a specific plan task completed.\n4. A sentinel with `**Status**: BLOCKED` is a failure, never a completion.\n\n## Examples (issue 42, plan task `implement-api` handled by builder)\n\n- Plan task:  `.kairon\u002Fartifacts\u002Fbuilder-42-implement-api.md`\n- Legacy\u002Fno-plan builder: `.kairon\u002Fartifacts\u002Fbuilder-42.md`\n","# Sentinel Protocol\n\nKairon detects agent\u002Ftask completion via **sentinel files** written to\n`.kairon\u002Fartifacts\u002F`, using a naming convention (NOT via agent JSON config\nfields). This skill is the single source of truth for that path format and the\nwrite rules. Every pipeline agent (architect, builder, validator, documenter)\nwrites a sentinel; krew-lead reads it. All of them reference this skill so the\nconvention is defined once.\n\n## Path Format\n\nPlan-based tasks (a task has an `id`):\n\n```\n.kairon\u002Fartifacts\u002F\u003Cagent>-\u003Cissue-number>-\u003Ctask-id>.md\n```\n\n- `\u003Cagent>` — the writing agent's name (e.g. `builder`, `validator`).\n- `\u003Cissue-number>` — the GitHub issue number being processed.\n- `\u003Ctask-id>` — the plan task's `id` field (unique per plan).\n\nIncluding `\u003Ctask-id>` is required: a single plan can assign several tasks to\nthe **same** agent (e.g. two `builder` tasks). Without the task id those tasks\nwould write and read the **same** file, so a later task could overwrite an\nearlier task's sentinel, or a completion check could misread a stale sentinel\nfrom a previous task as the current task's success.\n\n### Legacy \u002F non-plan fallback\n\nWhen there is no plan and therefore no task id (the legacy sequential\nworkflow), and for whole-issue signals that are not tied to a specific plan\ntask, use the task-less form:\n\n```\n.kairon\u002Fartifacts\u002F\u003Cagent>-\u003Cissue-number>.md\n```\n\nA reader that expects a plan task MUST use the `\u003Ctask-id>` form and MUST NOT\nfall back to the task-less form to satisfy a task-scoped check (that is exactly\nthe stale-read this protocol prevents).\n\n## Write Rules (writing agents)\n\n1. After completing your work, write your sentinel at the path above for your\n   agent name, the current issue number, and — for a plan task — the task id.\n2. Write to that path only. Do not write sentinels for other agents or tasks.\n3. Include a brief summary of what you produced so krew-lead can recover your\n   result from the file if your response is otherwise empty.\n4. A sentinel's presence with a success summary signals successful completion.\n5. If you could not deliver all of your assigned work, write the sentinel with\n   `**Status**: BLOCKED`, quote each item you could not deliver, and say why.\n   Never write a success summary for partial work. krew-lead treats BLOCKED as\n   a failure and escalates it to a human.\n\n## Read Rules (krew-lead)\n\n1. A plan task is complete only when its task-scoped sentinel\n   (`\u003Cagent>-\u003Cissue-number>-\u003Ctask-id>.md`) exists with a success status.\n2. On an empty subagent response, check for the sentinel before retrying:\n   `test -f .kairon\u002Fartifacts\u002F\u003Cagent>-\u003Cissue-number>-\u003Ctask-id>.md`; if it\n   exists, read it to recover the summary and continue; if missing, proceed\n   with normal retry escalation.\n3. Never accept a task-less sentinel as proof a specific plan task completed.\n4. A sentinel with `**Status**: BLOCKED` is a failure, never a completion.\n\n## Examples (issue 42, plan task `implement-api` handled by builder)\n\n- Plan task:  `.kairon\u002Fartifacts\u002Fbuilder-42-implement-api.md`\n- Legacy\u002Fno-plan builder: `.kairon\u002Fartifacts\u002Fbuilder-42.md`\n",{"name":5,"description":7},"main","ec7bf831c9ed4d0cf41b7bb12a058b07d4dfe296",".kiro\u002Fskills\u002Fsentinel-protocol",1,"https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon","https:\u002F\u002Fgithub.com\u002Fjbrinkman","https:\u002F\u002Fjoe.brinkman.me","I started as a self taught programmer more than 40 years ago while still in middle-school and I've never looked back. OSS advocate and public speaker.","2026-11-06 23:14:13",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jbrinkman\u002Fkairon --skill sentinel-protocol",{"tool":39,"command":40},"bunx","bunx skills add jbrinkman\u002Fkairon --skill sentinel-protocol",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jbrinkman\u002Fkairon --skill sentinel-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fsentinel-protocol\u002FSKILL.md",true,[],[48,55,62,68,73,80],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M73A2DA8HNMMJZPJ3A7CZKH0","selftest-conventions","Self-test override hook supplied by a case workspace fixture.","https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon\u002Fblob\u002Fmain\u002Finternal\u002Feval\u002Ftestdata\u002Fevals\u002Ffixtures\u002Fworkspaces\u002Fconventions\u002F.kiro\u002Fskills\u002Fselftest-conventions\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M73A2B3ZGQZMGDN5Z5SZ635A","engine-skill","Engine skill for the audit fixtures.","https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon\u002Fblob\u002Fmain\u002Finternal\u002Feval\u002Ftestdata\u002Faudit\u002Fok-hooks\u002Fskills\u002Fengine-skill\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M73A2993XGVZ84HJZQBDJ56M","demo-conventions","https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon\u002Fblob\u002Fmain\u002Finternal\u002Feval\u002Ftestdata\u002Faudit\u002Fok-hooks\u002Fskills\u002Fdemo-conventions\u002FSKILL.md",[],[],{"skillNo":69,"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":70,"categories":71,"keywords":72,"publishedAt":19},"01M73A26YG49RAENBTS83JJ7DD","https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon\u002Fblob\u002Fmain\u002Fcmd\u002Fkairon\u002Ftemplates\u002Fkiro\u002Fskills\u002Fsentinel-protocol\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M73A24HW4BG6MCAWVA5BM670","planner-shared","Kairon-managed contract shared by both planner agents. Defines the restrictions, the stage-output document the planner returns, how to investigate and classify a request, the issue-body standard and the hard bars.","https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon\u002Fblob\u002Fmain\u002Fcmd\u002Fkairon\u002Ftemplates\u002Fkiro\u002Fskills\u002Fplanner-shared\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M73A1ZQRKDZ7YM1AZVKWR4TC","validator-conventions","Structured templates and patterns for strict criterion-by-criterion validation. Enforces exact specification compliance and provides copy-paste report templates.","https:\u002F\u002Fgithub.com\u002Fjbrinkman\u002Fkairon\u002Fblob\u002Fmain\u002F.kiro\u002Fskills\u002Fvalidator-conventions\u002FSKILL.md",[],[]]