[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J4THMSWA1FC0AM76SGW3VH":3,"skill-same:01M6J4THMSWA1FC0AM76SGW3VH":84},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6J4THMSWA1FC0AM76SGW3VH","planr-share",null,"Share a status report, sprint note or release notes with the team as a chat message draft that the user approves and sends. Use when the user asks to post a planning update to chat.","openplanr\u002FOpenPlanr","openplanr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273764861?v=4","01M6J4PHHBPM1ATKH7TXR1AZMB","OpenPlanr","01M6J4PHNQ7FWP1CC3JGNVBQ8N",6,"MIT","https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-share\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"planr share","share","message","when","with","note","post","status report","sprint","as","draft","chat","status","use","team","release","report","planning","update","release notes","notes","2026-11-10 10:12:30",false,"---\nname: planr-share\ndescription: Share a status report, sprint note or release notes with the team as a chat message draft that the user approves and sends. Use when the user asks to post a planning update to chat.\nargument-hint: \"[status|sprint|release] [destination]\"\nlicense: MIT\n---\n\n# OpenPlanr Share\n\nTurn the current planning state into a team update and hand it to ~~chat as a\ndraft that the user reviews and sends. Perform the work in this session. Nothing\nleaves the session until the user approves the exact text and destination.\n\n## Choose the update\n\nThe first argument picks the source; default to `status`.\n\n- `status`: the delivery report `planr-status` gives. Read the planning artifacts\n  directly, or use `openplanr status --json` when it is available.\n- `sprint`: the current sprint under `.planr\u002Fsprints\u002F`: the one in progress, else\n  the most recent. Use its goal, selected items, progress and leftovers.\n- `release`: the newest release notes or changelog entry, or the version the\n  user names.\n\nWhen the working directory has no OpenPlanr planning files for the chosen source,\nsay so and ask which project to use, or stop. Never build an update from guesses.\n\nThe second argument is the destination: a channel or person. When it names a chat\nproduct from [connectors](references\u002Fconnectors.md) instead, use that product's\nconnection and still ask for the channel or person. When it is missing, ask for it.\nNever pick a destination yourself.\n\n## Write it\n\nLead with the outcome in one line, then at most ten short lines: what finished,\nwhat is in progress, what is blocked and who can unblock it, and what comes next.\nUse counts and dates, link pull requests or issues when their URLs are known, and\nleave out local file paths, backlog IDs and internal detail the team cannot act\non. Never include credentials or the contents of secret files.\n\nFormat the text for where it goes, as listed under \"Message format\" in\n[connectors](references\u002Fconnectors.md): when drafting through a connector, use the\nconnector's input format, and follow the connector tool's own description when it\nstates one; for text the user pastes, use the paste format. Use plain text when no\nformat is listed.\n\n## Preview, then ask\n\nShow the complete text exactly as it will appear, the destination, and what will\nhappen: \"create a draft in \u003Cdestination>; nothing is sent\". Ask through the host's\nstructured question surface, or one short chat question when there is none:\ncreate the draft, edit the text, or cancel. Create nothing without a clear yes.\nAfter an edit, preview again.\n\n## If ~~chat is connected\n\nA category is connected when the host exposes a tool for one of its products,\nloaded or deferred. On approval, use that connection to create a message draft\nin the destination, then report where the draft is and that the user sends it\nfrom the chat app.\n\n- Send directly only when the user explicitly asks to send and the connection\n  can send; confirm the destination once more first.\n- When the connection cannot create drafts, say so and offer to send on an\n  explicit request, or print the text instead.\n- When the connection fails, for example because a workspace admin has not\n  approved the app, report the error, print the text ready to paste, and stop.\n\n## With nothing connected\n\nPrint the update ready to paste and the one connect step for the current host\nfrom [connectors](references\u002Fconnectors.md), and suggest `\u002Fplanr-connect`. Make no\nremote call and do not retry; the user runs this skill again once connected.\n\n## Rules\n\n- Never ask for, read, store or print a token, key or password, and never edit\n  host configuration.\n- One destination per run.\n- Never change planning files.\n\n## Return\n\nLead with the result: draft created (where), sent (where, on explicit request),\nprinted for pasting, or cancelled. Name the source used and any section that was\nempty or unavailable.\n","# OpenPlanr Share\n\nTurn the current planning state into a team update and hand it to ~~chat as a\ndraft that the user reviews and sends. Perform the work in this session. Nothing\nleaves the session until the user approves the exact text and destination.\n\n## Choose the update\n\nThe first argument picks the source; default to `status`.\n\n- `status`: the delivery report `planr-status` gives. Read the planning artifacts\n  directly, or use `openplanr status --json` when it is available.\n- `sprint`: the current sprint under `.planr\u002Fsprints\u002F`: the one in progress, else\n  the most recent. Use its goal, selected items, progress and leftovers.\n- `release`: the newest release notes or changelog entry, or the version the\n  user names.\n\nWhen the working directory has no OpenPlanr planning files for the chosen source,\nsay so and ask which project to use, or stop. Never build an update from guesses.\n\nThe second argument is the destination: a channel or person. When it names a chat\nproduct from [connectors](references\u002Fconnectors.md) instead, use that product's\nconnection and still ask for the channel or person. When it is missing, ask for it.\nNever pick a destination yourself.\n\n## Write it\n\nLead with the outcome in one line, then at most ten short lines: what finished,\nwhat is in progress, what is blocked and who can unblock it, and what comes next.\nUse counts and dates, link pull requests or issues when their URLs are known, and\nleave out local file paths, backlog IDs and internal detail the team cannot act\non. Never include credentials or the contents of secret files.\n\nFormat the text for where it goes, as listed under \"Message format\" in\n[connectors](references\u002Fconnectors.md): when drafting through a connector, use the\nconnector's input format, and follow the connector tool's own description when it\nstates one; for text the user pastes, use the paste format. Use plain text when no\nformat is listed.\n\n## Preview, then ask\n\nShow the complete text exactly as it will appear, the destination, and what will\nhappen: \"create a draft in \u003Cdestination>; nothing is sent\". Ask through the host's\nstructured question surface, or one short chat question when there is none:\ncreate the draft, edit the text, or cancel. Create nothing without a clear yes.\nAfter an edit, preview again.\n\n## If ~~chat is connected\n\nA category is connected when the host exposes a tool for one of its products,\nloaded or deferred. On approval, use that connection to create a message draft\nin the destination, then report where the draft is and that the user sends it\nfrom the chat app.\n\n- Send directly only when the user explicitly asks to send and the connection\n  can send; confirm the destination once more first.\n- When the connection cannot create drafts, say so and offer to send on an\n  explicit request, or print the text instead.\n- When the connection fails, for example because a workspace admin has not\n  approved the app, report the error, print the text ready to paste, and stop.\n\n## With nothing connected\n\nPrint the update ready to paste and the one connect step for the current host\nfrom [connectors](references\u002Fconnectors.md), and suggest `\u002Fplanr-connect`. Make no\nremote call and do not retry; the user runs this skill again once connected.\n\n## Rules\n\n- Never ask for, read, store or print a token, key or password, and never edit\n  host configuration.\n- One destination per run.\n- Never change planning files.\n\n## Return\n\nLead with the result: draft created (where), sent (where, on explicit request),\nprinted for pasting, or cancelled. Name the source used and any section that was\nempty or unavailable.\n",{"name":5,"license":15,"description":7,"argument-hint":45},"[status|sprint|release] [destination]","main","8e3991b4f17b5619cf939a6fa06d45bca8115d98","skills\u002Fplanr-share",1,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr","https:\u002F\u002Fopenplanr.dev","https:\u002F\u002Fgithub.com\u002Fopenplanr","https:\u002F\u002Fopenplanr.dev\u002F","Close the loop from intent to delivery. The open harness around your coding agent.","2026-11-11 21:48:23",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add openplanr\u002FOpenPlanr --skill planr-share",{"tool":62,"command":63},"bunx","bunx skills add openplanr\u002FOpenPlanr --skill planr-share",{"tool":65,"command":66},"pnpm","pnpm dlx skills add openplanr\u002FOpenPlanr --skill planr-share","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-share\u002FSKILL.md",true,[70,76,80],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",397,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-share\u002Fagents\u002Fopenai.yaml",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"openplanr.skill.json",687,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-share\u002Fopenplanr.skill.json",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fconnectors.md",5264,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-share\u002Freferences\u002Fconnectors.md",[85,101,118,137,159,177],{"skillNo":86,"name":87,"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":88,"categories":89,"keywords":100,"publishedAt":40},"01M70XD1RYQC5160MRRCPTGA2K","design","https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Ftests\u002Frelease-train\u002Ffixtures\u002Ffigma\u002Fskills\u002Fdesign\u002FSKILL.md",[90,95],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[87],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":40},"01M6J4V75T3VW91HJQ5ZD5SFW0","planr-sync","Audit OpenPlanr planning artifacts for graph and protocol drift. Use when statuses, references, schemas, or generated planning views may be inconsistent.","https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-sync\u002FSKILL.md",[],[108,109,110,22,111,112,113,114,115,116,32,117,36],"sync","planr sync","generated","graph","protocol","audit","references","drift","artifacts","for",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":40},"01M6J4V38R89DYYA4AAN312MNZ","planr-status","Inspect project delivery or one feature's pipeline status without changing state. Use when the user asks what is done, pending, blocked, or next.","https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-status\u002FSKILL.md",[],[31,125,126,127,128,32,129,130,131,132,133,134,22,135,136],"planr status","next","state","done","inspect","pipeline","project","feature","delivery","pending","pipeline status","user",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":146,"publishedAt":40},"01M6J4TYGNBZG2YSSHCY8BASFB","planr-sprint","Refine every open backlog item against the code and the calendar, refute the picks, and select a sprint that fits capacity and the release cut. Use before a cut or sprint; not for decomposing one specification or reporting status.","https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-sprint\u002FSKILL.md",[143],{"categoryNo":144,"categoryName":145,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000030","开发工程师",[147,27,34,148,32,149,150,117,31,151,152,153,154,155,156,157,158],"planr sprint","capacity","release cut","backlog","refine","reporting","calendar","cut","specification","code","open","select",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":40},"01M6J4TT7X6GV9A25JHSMKEMHJ","planr-spec","Shape vague product or engineering intent into a clear, measurable Protocol-compatible specification grounded in the current repository. Use when requirements need clarification before planning or implementation.","https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-spec\u002FSKILL.md",[],[166,167,168,32,36,169,170,22,171,172,112,173,174,175,176,155],"spec","planr spec","requirements","vague","engineering","implementation","clear","shape","repository","product","intent",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":40},"01M6J4TNYE49SE8PBNNWJKK1CN","planr-ship","Implement an OpenPlanr plan, specification, task, or clearly stated request end to end in the current repository. Use when the user asks to build, implement, fix, finish, or ship local work, or to plan and implement an accepted change. Invoke before editing files for the requested change. Not for planning only, landing, release, or work handed to another coding agent.","https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-ship\u002FSKILL.md",[],[184,185,186,187,188,189,190,191,192,193,194,22,195,196,197,117,36,198,199,34,174,200,155,201],"ship","planr ship","local","only","end","fix","coding agent","work","plan","plan and implement","request","invoke","landing","editing","coding","finish","files","change"]