[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXYANN7YXQRQ1QV7HTX7SB":3,"skill-same:01M6DXYANN7YXQRQ1QV7HTX7SB":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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":63},"01M6DXYANN7YXQRQ1QV7HTX7SB","plan-review-output-format",null,"Output format specification for plan review agents. Defines the JSON schema, field reference, severity emoji prefixes, and finding body format for plan reviews.","atomicinnovation\u002Faccelerator","atomicinnovation","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F65866524?v=4","01M6DXP513JV585FN2QPNR6079","Atomic","01M6DXP55MPK99YVZ2HGMEN991",34,"MIT","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Freview\u002Foutput-formats\u002Fplan-review-output-format\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"plan","format","plan review","output","review","plan review output format","specification","body","for","true","reviews","false","emoji","reference","schema","json","severity","json schema","2026-11-10 10:12:30",false,"---\nname: plan-review-output-format\ndescription: Output format specification for plan review agents. Defines the\n  JSON schema, field reference, severity emoji prefixes, and finding body format\n  for plan reviews.\nuser-invocable: false\ndisable-model-invocation: true\n---\n\n# Plan Review Output Format\n\n## JSON Schema\n\nReturn your analysis as a JSON code block. Do not include any text before or\nafter the JSON block — the orchestrator will parse this output directly.\n\n```json\n{\n  \"lens\": \"\u003Clens-identifier>\",\n  \"summary\": \"2-3 sentence assessment from this lens perspective.\",\n  \"strengths\": [\n    \"Positive observation about what the plan gets right from this lens perspective\"\n  ],\n  \"findings\": [\n    {\n      \"severity\": \"critical\",\n      \"confidence\": \"high\",\n      \"lens\": \"\u003Clens-identifier>\",\n      \"location\": \"Phase 2, Section 3: Database Migration\",\n      \"title\": \"Brief finding title\",\n      \"body\": \"? **\u003CLens Name>**\\n\\n[Issue description — 1-2 sentences with enough context to understand standalone].\\n\\n**Impact**: [Why this matters — 1 sentence].\\n\\n**Suggestion**: [Concrete fix — 1-2 sentences].\"\n    }\n  ]\n}\n```\n\n## Field Reference\n\n- **lens**: Agent lens identifier (e.g., `\"architecture\"`, `\"security\"`,\n  `\"test-coverage\"`, `\"code-quality\"`, `\"standards\"`, `\"usability\"`,\n  `\"performance\"`, `\"documentation\"`, `\"database\"`, `\"correctness\"`,\n  `\"compatibility\"`, `\"portability\"`, `\"safety\"`)\n- **summary**: 2-3 sentence assessment from this lens perspective. Reflect the\n  key dimensions from the lens's Core Responsibilities. This is where holistic\n  assessment lives, beyond individual findings.\n- **strengths**: Positive observations (fed into the review summary — never\n  posted as individual findings)\n- **findings**: All findings, each referencing a location in the plan\n  - **severity**: One of `\"critical\"`, `\"major\"`, `\"minor\"`, `\"suggestion\"`\n  - **confidence**: One of `\"high\"`, `\"medium\"`, `\"low\"`\n  - **lens**: The lens identifier (same value as the top-level `lens` field).\n    Included on each finding so the orchestrator can attribute findings after\n    merging outputs from multiple agents.\n  - **location**: Human-readable reference to the plan section where the\n    finding is most relevant (e.g., \"Phase 2: API Endpoints\",\n    \"Implementation Approach\", \"Phase 1: Data Model\")\n  - **title**: Brief title for the finding (used in the summary index)\n  - **body**: Self-contained finding body. See \"Finding Body Format\" below.\n\n## Severity Emoji Prefixes\n\nUse these **actual Unicode emoji characters** at the start of each finding `body`:\n- `?` for `\"critical\"` severity\n- `?` for `\"major\"` severity\n- `?` for `\"minor\"` and `\"suggestion\"` severity\n\n**IMPORTANT**: Use the actual Unicode emoji characters shown above (? ? ?), NOT\ntext shortcodes like `:red_circle:`, `:yellow_circle:`, or `:blue_circle:`. The\noutput is rendered as markdown, not Slack\u002FDiscord, so shortcodes will appear as\nliteral text.\n\n## Finding Body Format\n\nEach finding `body` should follow this structure:\n\n```\n[emoji] **[Lens Name]**\n\n[Issue description — 1-2 sentences, standalone context].\n\n**Impact**: [Why this matters].\n\n**Suggestion**: [Concrete fix].\n```\n\nExample:\n\n```\n? **Architecture**\n\nThe plan proposes a direct dependency from the API layer to the database schema\nwith no service abstraction. This couples the presentation layer to the data\nmodel.\n\n**Impact**: Database schema changes will ripple into the API layer, breaking\nthe dependency rule.\n\n**Suggestion**: Introduce a service layer to mediate between the API handlers\nand the data access layer.\n```\n\n**Output only the JSON block** — do not include additional prose, narrative\nanalysis, or markdown outside the JSON code fence. The orchestrator parses\nyour output as JSON.\n","# Plan Review Output Format\n\n## JSON Schema\n\nReturn your analysis as a JSON code block. Do not include any text before or\nafter the JSON block — the orchestrator will parse this output directly.\n\n```json\n{\n  \"lens\": \"\u003Clens-identifier>\",\n  \"summary\": \"2-3 sentence assessment from this lens perspective.\",\n  \"strengths\": [\n    \"Positive observation about what the plan gets right from this lens perspective\"\n  ],\n  \"findings\": [\n    {\n      \"severity\": \"critical\",\n      \"confidence\": \"high\",\n      \"lens\": \"\u003Clens-identifier>\",\n      \"location\": \"Phase 2, Section 3: Database Migration\",\n      \"title\": \"Brief finding title\",\n      \"body\": \"? **\u003CLens Name>**\\n\\n[Issue description — 1-2 sentences with enough context to understand standalone].\\n\\n**Impact**: [Why this matters — 1 sentence].\\n\\n**Suggestion**: [Concrete fix — 1-2 sentences].\"\n    }\n  ]\n}\n```\n\n## Field Reference\n\n- **lens**: Agent lens identifier (e.g., `\"architecture\"`, `\"security\"`,\n  `\"test-coverage\"`, `\"code-quality\"`, `\"standards\"`, `\"usability\"`,\n  `\"performance\"`, `\"documentation\"`, `\"database\"`, `\"correctness\"`,\n  `\"compatibility\"`, `\"portability\"`, `\"safety\"`)\n- **summary**: 2-3 sentence assessment from this lens perspective. Reflect the\n  key dimensions from the lens's Core Responsibilities. This is where holistic\n  assessment lives, beyond individual findings.\n- **strengths**: Positive observations (fed into the review summary — never\n  posted as individual findings)\n- **findings**: All findings, each referencing a location in the plan\n  - **severity**: One of `\"critical\"`, `\"major\"`, `\"minor\"`, `\"suggestion\"`\n  - **confidence**: One of `\"high\"`, `\"medium\"`, `\"low\"`\n  - **lens**: The lens identifier (same value as the top-level `lens` field).\n    Included on each finding so the orchestrator can attribute findings after\n    merging outputs from multiple agents.\n  - **location**: Human-readable reference to the plan section where the\n    finding is most relevant (e.g., \"Phase 2: API Endpoints\",\n    \"Implementation Approach\", \"Phase 1: Data Model\")\n  - **title**: Brief title for the finding (used in the summary index)\n  - **body**: Self-contained finding body. See \"Finding Body Format\" below.\n\n## Severity Emoji Prefixes\n\nUse these **actual Unicode emoji characters** at the start of each finding `body`:\n- `?` for `\"critical\"` severity\n- `?` for `\"major\"` severity\n- `?` for `\"minor\"` and `\"suggestion\"` severity\n\n**IMPORTANT**: Use the actual Unicode emoji characters shown above (? ? ?), NOT\ntext shortcodes like `:red_circle:`, `:yellow_circle:`, or `:blue_circle:`. The\noutput is rendered as markdown, not Slack\u002FDiscord, so shortcodes will appear as\nliteral text.\n\n## Finding Body Format\n\nEach finding `body` should follow this structure:\n\n```\n[emoji] **[Lens Name]**\n\n[Issue description — 1-2 sentences, standalone context].\n\n**Impact**: [Why this matters].\n\n**Suggestion**: [Concrete fix].\n```\n\nExample:\n\n```\n? **Architecture**\n\nThe plan proposes a direct dependency from the API layer to the database schema\nwith no service abstraction. This couples the presentation layer to the data\nmodel.\n\n**Impact**: Database schema changes will ripple into the API layer, breaking\nthe dependency rule.\n\n**Suggestion**: Introduce a service layer to mediate between the API handlers\nand the data access layer.\n```\n\n**Output only the JSON block** — do not include additional prose, narrative\nanalysis, or markdown outside the JSON code fence. The orchestrator parses\nyour output as JSON.\n",{"name":5,"description":7,"user-invocable":38,"disable-model-invocation":42},true,"main","007b2dd695b63c2f097cdc40e54229b6e8b4596a","skills\u002Freview\u002Foutput-formats\u002Fplan-review-output-format",2,"https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator","https:\u002F\u002Fgo-atomic.io","https:\u002F\u002Fgithub.com\u002Fatomicinnovation","2026-11-13 08:45:04",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":42},[53,56,59],{"tool":54,"command":55},"npx","npx skills add atomicinnovation\u002Faccelerator --skill plan-review-output-format",{"tool":57,"command":58},"bunx","bunx skills add atomicinnovation\u002Faccelerator --skill plan-review-output-format",{"tool":60,"command":61},"pnpm","pnpm dlx skills add atomicinnovation\u002Faccelerator --skill plan-review-output-format","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Freview\u002Foutput-formats\u002Fplan-review-output-format\u002FSKILL.md",[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fstyle.md","REFERENCE","参考文档",58,"https:\u002F\u002Fgithub.com\u002Fbenjamincanac\u002Fnuxt-agent-discovery\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Funit-skills\u002Fskills\u002Fwriting\u002Freferences\u002Fstyle.md",[71,107,132,154,169,194],{"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":87,"publishedAt":37},"01M70S7PFGVATJREBFEGPJB718","explore-pr","Build an interactive, design-first and picture-first exploration page for a pull request — its architecture, abstractions and design decisions drawn as diagrams, a guided tour in reading order with code as the evidence, an attention map of where the risk sits, a ledger of its riskiest operations, prior review findings re-checked against the code, and simulations specific to the PR — with the reviewer's verdicts and notes saved. Use when the user wants to explore, understand or review a large pull request or its design, asks for a review page, walkthrough or visual explanation of a PR, or is struggling to review a big change.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fexplore-pr\u002FSKILL.md",[77,82],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":83,"categoryName":84,"taxonomyType":85,"taxonomyTypeDesc":86},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,23,105,106],"explore pr","explore","pr","diagrams","exploration","re","review findings","walkthrough","design","map","when","number","URL","Bash","code","architecture","reviewer","notes","change",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":37},"01M6DY04WBTMFV96JMBP5ZXVFX","update-work-item","Update fields (status, priority, tags, parent, etc.) of an existing work item. Use to transition status, change priority, manage tags, or edit any frontmatter field. No transition enforcement — arbitrary changes are allowed.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fupdate-work-item\u002FSKILL.md",[],[114,115,116,117,118,119,120,101,106,121,122,123,124,125,126,127,128,129,130,131],"work","update","update work item","work item","enforcement","manage","use","config","edit","validate","status","transition","frontmatter","Existing","tags","changes","fields","op",{"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},"01M6DY0106CF15CYEJHZM14GBZ","sync-work-items","Reconcile local work items in meta\u002Fwork\u002F with the active remote tracker named by work.integration. Use when the user wants to sync, push, or pull work items to or from Jira or Linear, preview what a sync would change, or reconcile divergent local and remote state.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fsync-work-items\u002FSKILL.md",[],[114,139,140,141,142,143,144,101,145,106,146,147,148,149,150,151,152,121,153,126,98],"sync","sync work items","promote","Meta","local","only","preview","active","tracker","max","jira","remote","create","adopt","reconcile",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":37},"01M6HNF86984S4XK21Q26VZA21","sync-work-items-recovery","Recovery procedures for work sync failures that need a person — terminal rows, refused pending pushes and refused orders. Read by sync-work-items — not invoked directly.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fsync-work-items-recovery\u002FSKILL.md",[],[161,114,162,139,140,163,27,164,165,166,28,30,167,168],"sync work items recovery","recovery","work-items","terminal","read","person","orders","pending",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":37},"01M6DXZWH7PR72VCEXSSD4XNK4","stress-test-work-item","Interactively stress-test a work item by grilling the user on scope, assumptions, acceptance criteria, edge cases, and dependencies to surface issues, gaps, and flawed assumptions before implementation is planned.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Fstress-test-work-item\u002FSKILL.md",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000008","测试与质量",[179,180,114,181,117,182,183,184,185,186,187,101,188,189,121,123,190,191,192,99,193,126],"stress test","test","stress test work item","stress","scope","issues","edge","stress-test","acceptance","acceptance criteria","dependencies","implementation","grilling","user","gaps",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":37},"01M6DXZRQWHTWV1G9PTTHCGGYA","review-work-item","Review a work item through multiple quality lenses and collaboratively iterate based on findings. Use when the user wants to evaluate a work item before implementation or escalation.","https:\u002F\u002Fgithub.com\u002Fatomicinnovation\u002Faccelerator\u002Fblob\u002Fmain\u002Fskills\u002Fwork\u002Freview-work-item\u002FSKILL.md",[],[23,114,201,117,202,203,120,101,204,205,121,123,190,192,206,98,207,208,126,209],"review work item","review work","escalation","file","quality","metadata","iterate","evaluate","path"]