[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTD0FPHTCQ32APQ2SZYP64":3,"skill-same:01M6CTD0FPHTCQ32APQ2SZYP64":60},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":53},"01M6CTD0FPHTCQ32APQ2SZYP64","decision-memo-writer",null,"Writes a decision record with rationale, alternatives considered and consequences. Use when a non-trivial decision needs to be understood later.","vibbs\u002Fcompany-os","vibbs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7379149?v=4","01M6CT6M03CAS1H7RA89F3965B","Vibbs Dod","01M6CT6M4MY60C9FFQ3AAR2RSK",6,"MIT","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fdecision-memo-writer\u002FSKILL.md",[],[19,20,21,22,23,24],"decision","writer","decision memo writer","use","later","record","2026-11-10 10:12:30",false,"---\nname: decision-memo-writer\ndescription: Writes a decision record with rationale, alternatives considered and consequences. Use when a non-trivial decision needs to be understood later.\nruntimes:\n  claude:\n    user-invocable: true\n---\n\n# Decision Memo Writer\n\n## Reference\n- **ID**: S-ORG-02\n- **Category**: Orchestration\n- **Inputs**: decision context, alternatives, stakeholder positions\n- **Outputs**: decision memo artifact → artifacts\u002Fdecision-memos\u002F\n- **Used by**: Orchestrator Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\nRecords non-trivial decisions with full rationale, alternatives evaluated, and anticipated consequences so that future team members can understand why a particular path was chosen without re-litigating the discussion.\n\n## Procedure\n\n### ID Convention\nUse the format `DM-{NNN}` for decision memo IDs (e.g., DM-001, DM-002). For specialized memos, use prefixes:\n- `REVIEW-` for review memos (e.g., REVIEW-WEEKLY-2026-03-01)\n- `RETRO-` for retrospective memos (e.g., RETRO-PRD-001)\n- `GROWTH-` for growth experiment memos (e.g., GROWTH-001)\n- `CONV-` for customer conversation logs (e.g., CONV-001)\n\nCheck `artifacts\u002Fdecision-memos\u002F` for existing IDs to avoid collisions.\n\n### Steps\n1. Gather the decision context: what problem or question triggered this decision.\n2. List all alternatives considered, including the status-quo option.\n3. For each alternative, document pros, cons, risks, and estimated effort.\n4. Identify stakeholder positions and any dissenting opinions.\n5. State the chosen alternative and the primary rationale for selection.\n6. Document expected consequences (positive and negative) of the decision.\n7. Define revisit criteria — conditions under which this decision should be reconsidered.\n8. Write the memo in the standard template and save to `artifacts\u002Fdecision-memos\u002F`.\n9. Validate the artifact using `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`.\n\n## Quality Checklist\n- [ ] Decision context is clearly stated and specific\n- [ ] At least two alternatives (including status-quo) are documented\n- [ ] Each alternative has pros, cons, and risk assessment\n- [ ] Stakeholder positions are captured accurately\n- [ ] Chosen alternative has explicit rationale\n- [ ] Consequences section covers both upside and downside\n- [ ] Revisit criteria are defined with measurable triggers\n- [ ] Artifact passes validation\n","# Decision Memo Writer\n\n## Reference\n- **ID**: S-ORG-02\n- **Category**: Orchestration\n- **Inputs**: decision context, alternatives, stakeholder positions\n- **Outputs**: decision memo artifact → artifacts\u002Fdecision-memos\u002F\n- **Used by**: Orchestrator Agent\n- **Tool scripts**: .\u002Ftools\u002Fartifact\u002Fvalidate.sh\n\n## Purpose\nRecords non-trivial decisions with full rationale, alternatives evaluated, and anticipated consequences so that future team members can understand why a particular path was chosen without re-litigating the discussion.\n\n## Procedure\n\n### ID Convention\nUse the format `DM-{NNN}` for decision memo IDs (e.g., DM-001, DM-002). For specialized memos, use prefixes:\n- `REVIEW-` for review memos (e.g., REVIEW-WEEKLY-2026-03-01)\n- `RETRO-` for retrospective memos (e.g., RETRO-PRD-001)\n- `GROWTH-` for growth experiment memos (e.g., GROWTH-001)\n- `CONV-` for customer conversation logs (e.g., CONV-001)\n\nCheck `artifacts\u002Fdecision-memos\u002F` for existing IDs to avoid collisions.\n\n### Steps\n1. Gather the decision context: what problem or question triggered this decision.\n2. List all alternatives considered, including the status-quo option.\n3. For each alternative, document pros, cons, risks, and estimated effort.\n4. Identify stakeholder positions and any dissenting opinions.\n5. State the chosen alternative and the primary rationale for selection.\n6. Document expected consequences (positive and negative) of the decision.\n7. Define revisit criteria — conditions under which this decision should be reconsidered.\n8. Write the memo in the standard template and save to `artifacts\u002Fdecision-memos\u002F`.\n9. Validate the artifact using `.\u002Ftools\u002Fartifact\u002Fvalidate.sh`.\n\n## Quality Checklist\n- [ ] Decision context is clearly stated and specific\n- [ ] At least two alternatives (including status-quo) are documented\n- [ ] Each alternative has pros, cons, and risk assessment\n- [ ] Stakeholder positions are captured accurately\n- [ ] Chosen alternative has explicit rationale\n- [ ] Consequences section covers both upside and downside\n- [ ] Revisit criteria are defined with measurable triggers\n- [ ] Artifact passes validation\n",{"name":5,"runtimes":30,"description":7},{"claude":31},{"user-invocable":32},true,"main","e842fb6d0e04360c47db78bc2e2e2987314d64d4","os\u002Fskills\u002Fdecision-memo-writer",2,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os","https:\u002F\u002Fgithub.com\u002Fvibbs","Principal Engineer · Applied AI · building ArcAI @ GrowthArc","2026-10-21 02:08:08",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":32},[43,46,49],{"tool":44,"command":45},"npx","npx skills add vibbs\u002Fcompany-os --skill decision-memo-writer",{"tool":47,"command":48},"bunx","bunx skills add vibbs\u002Fcompany-os --skill decision-memo-writer",{"tool":50,"command":51},"pnpm","pnpm dlx skills add vibbs\u002Fcompany-os --skill decision-memo-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fdecision-memo-writer\u002FSKILL.md",[54],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"decision-memo-template.md","REFERENCE","参考文档",660,"https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fdecision-memo-writer\u002Fdecision-memo-template.md",[61,70,78,88,104,122],{"skillNo":62,"name":63,"nameZh":6,"description":64,"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":25},"01M6CTHBW1E64ECYGD105N4S5E","typo-field","Fixture skill with a misspelled top-level field.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Ftypo-field\u002FSKILL.md",[],[68,69],"typo field","fixture skill",{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":25},"01M6CTHABTV8FKVDHFMMKPAV51","spaced-comments","Fixture skill with comments and spaces after block keys.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fspaced-comments\u002FSKILL.md",[],[77,69],"spaced comments",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":25},"01M6CTH8MHC14KB65ZDHYBJW1N","crlf-comments","Fixture skill with Windows line endings.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fcrlf-comments\u002FSKILL.md",[],[85,86,87,69],"crlf comments","CRLF","windows",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":25},"01M6CTH6TBKTDP9G8QB1Z2K0TY","claude-fields","Fixture skill using top-level fields Claude Code documents.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fclaude-fields\u002FSKILL.md",[],[95,96,97,98,99,100,69,101,102,103],"claude fields","explore","documents","src","grep","read","Bash","code","testing",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":115,"publishedAt":25},"01M6CTH46BGKXH80RWS876Y2CW","workflow-router","Maps an objective to the artifacts, stages and agents it needs. Use when deciding what happens next or which agents to involve.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[116,117,118,119,120,22,121],"workflow","router","workflow router","next","maps","artifacts",{"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":25},"01M6CTH27653SRVP2FMEQN3J5B","weekly-review","Summarizes your week: what shipped, AI spend, support themes, security health and next priorities. Use at the end of each week.","https:\u002F\u002Fgithub.com\u002Fvibbs\u002Fcompany-os\u002Fblob\u002Fmain\u002Fos\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[129,130,131,119,22,132,133,134,135],"weekly review","review","priorities","health","save","support","security"]