[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6J4R8DTSXRF7RQEW3VMM0YY":3,"skill-same:01M6J4R8DTSXRF7RQEW3VMM0YY":98},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6J4R8DTSXRF7RQEW3VMM0YY","planr-cto-review",null,"Produce a grounded technology and delivery-risk review for an Operate cycle. Use when architecture, reliability, security, or execution risk needs a CTO lens.","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-cto-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"planr cto review","cto","cto review","review","cycle","when","for","operate","lens","technology","delivery","reliability","use","risk","execution","produce","architecture","security","2026-11-10 10:12:30",false,"---\nname: planr-cto-review\ndescription: \"Produce a grounded technology and delivery-risk review for an Operate cycle. Use when architecture, reliability, security, or execution risk needs a CTO lens.\"\nlicense: MIT\n---\n\n# OpenPlanr CTO Review\n\n## Shared contract\n\nRead [the shared advisor contract](references\u002Foperate-advisor-contract.md) before reviewing. It\nowns the common context method, grounding standard, output schema, and optional local validator.\n\n## Role identity\n\n- Executive label: `CTO`\n- Role ID: `technology-risk`\n- Scope: Technology leverage, architecture, security, delivery risk, and technical constraints.\n- Capability ceiling: `read-only`\n\n## Questions this lens must cover\n\n1. Which technical constraints now block a stated objective?\n2. Which technical risks are most decision-relevant from current evidence, and which remain\n   unranked because no common comparison exists?\n3. Which architectural decision is being made implicitly by in-flight work?\n4. How reversible are the highest-impact evidenced changes?\n\n## Evidence to seek\n\n- Current repository, architecture, infrastructure, CI, security, and deployment evidence.\n- Incidents, failed releases, recovery notes, test results, and production-readiness records.\n- Exposure, affected surface, control state, reversibility, and the objective each constraint blocks.\n\n## Decision standard\n\n- A risk names likelihood or observed frequency, impact, exposure, and reversibility.\n- Separate an observed failure from an inferred future risk.\n- Do not present architectural preference or generic technical debt as business risk.\n- Surface evidence-backed security and operational risks even when no portfolio-wide ranking can\n  be established.\n\n## Outside this lens\n\nCode-level refactoring instructions, product prioritization, campaign decisions, and authority to\noperate production systems.\n\n## Return\n\nUse the shared advisor contract's concise return: lead with the grounded signal\nand recommendation, link the note, summarize findings and actual checks, and\nidentify any decision-changing evidence gap. Keep the full review in its durable\nnote; different chat wording never requires another review or corrective run.\n","# OpenPlanr CTO Review\n\n## Shared contract\n\nRead [the shared advisor contract](references\u002Foperate-advisor-contract.md) before reviewing. It\nowns the common context method, grounding standard, output schema, and optional local validator.\n\n## Role identity\n\n- Executive label: `CTO`\n- Role ID: `technology-risk`\n- Scope: Technology leverage, architecture, security, delivery risk, and technical constraints.\n- Capability ceiling: `read-only`\n\n## Questions this lens must cover\n\n1. Which technical constraints now block a stated objective?\n2. Which technical risks are most decision-relevant from current evidence, and which remain\n   unranked because no common comparison exists?\n3. Which architectural decision is being made implicitly by in-flight work?\n4. How reversible are the highest-impact evidenced changes?\n\n## Evidence to seek\n\n- Current repository, architecture, infrastructure, CI, security, and deployment evidence.\n- Incidents, failed releases, recovery notes, test results, and production-readiness records.\n- Exposure, affected surface, control state, reversibility, and the objective each constraint blocks.\n\n## Decision standard\n\n- A risk names likelihood or observed frequency, impact, exposure, and reversibility.\n- Separate an observed failure from an inferred future risk.\n- Do not present architectural preference or generic technical debt as business risk.\n- Surface evidence-backed security and operational risks even when no portfolio-wide ranking can\n  be established.\n\n## Outside this lens\n\nCode-level refactoring instructions, product prioritization, campaign decisions, and authority to\noperate production systems.\n\n## Return\n\nUse the shared advisor contract's concise return: lead with the grounded signal\nand recommendation, link the note, summarize findings and actual checks, and\nidentify any decision-changing evidence gap. Keep the full review in its durable\nnote; different chat wording never requires another review or corrective run.\n",{"name":5,"license":15,"description":7},"main","8e3991b4f17b5619cf939a6fa06d45bca8115d98","skills\u002Fplanr-cto-review",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-12 12:17:02",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add openplanr\u002FOpenPlanr --skill planr-cto-review",{"tool":58,"command":59},"bunx","bunx skills add openplanr\u002FOpenPlanr --skill planr-cto-review",{"tool":61,"command":62},"pnpm","pnpm dlx skills add openplanr\u002FOpenPlanr --skill planr-cto-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-cto-review\u002FSKILL.md",true,[66,72,76,80,86,90,94],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"agents\u002Fopenai.yaml","REFERENCE","参考文档",384,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-cto-review\u002Fagents\u002Fopenai.yaml",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"openplanr.skill.json",1546,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-cto-review\u002Fopenplanr.skill.json",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Foperate-advisor-contract.md",6231,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-cto-review\u002Freferences\u002Foperate-advisor-contract.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Ferrors.mjs","SCRIPT","脚本",205,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-cto-review\u002Fscripts\u002Ferrors.mjs",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Foperate-review-contract.mjs",12361,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-cto-review\u002Fscripts\u002Foperate-review-contract.mjs",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Foperate-review-note.mjs",23885,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-cto-review\u002Fscripts\u002Foperate-review-note.mjs",{"path":95,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fvalidate-note.mjs",1309,"https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Fskills\u002Fplanr-cto-review\u002Fscripts\u002Fvalidate-note.mjs",[99,115,132,151,175,193],{"skillNo":100,"name":101,"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":102,"categories":103,"keywords":114,"publishedAt":37},"01M70XD1RYQC5160MRRCPTGA2K","design","https:\u002F\u002Fgithub.com\u002Fopenplanr\u002FOpenPlanr\u002Fblob\u002Fmain\u002Ftests\u002Frelease-train\u002Ffixtures\u002Ffigma\u002Fskills\u002Fdesign\u002FSKILL.md",[104,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[101],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":37},"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",[],[122,123,124,24,125,126,127,128,129,130,31,25,131],"sync","planr sync","generated","graph","protocol","audit","references","drift","artifacts","planning",{"skillNo":133,"name":134,"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":37},"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",[],[139,140,141,142,143,31,144,145,146,147,29,148,24,149,150],"status","planr status","next","state","done","inspect","pipeline","project","feature","pending","pipeline status","user",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":160,"publishedAt":37},"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",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000030","开发工程师",[161,162,163,164,31,165,166,25,139,167,168,169,170,171,172,173,174],"planr sprint","sprint","release","capacity","release cut","backlog","refine","reporting","calendar","cut","specification","code","open","select",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":37},"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",[],[182,183,184,31,131,185,186,24,187,188,126,189,190,191,192,171],"spec","planr spec","requirements","vague","engineering","implementation","clear","shape","repository","product","intent",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":37},"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",[],[200,201,202,203,204,205,206,207,208,209,210,24,211,212,213,25,131,214,215,163,190,216,171,217],"ship","planr ship","local","only","end","fix","coding agent","work","plan","plan and implement","request","invoke","landing","editing","coding","finish","files","change"]