[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NXASSWS6FRE0CGKQJ9EF51":3,"skill-same:01M6NXASSWS6FRE0CGKQJ9EF51":153},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6NXASSWS6FRE0CGKQJ9EF51","ccpm",null,"CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue\u002FPR operations with no delivery context.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"next","spec-driven","closing","streams","scope","progress","project","time","delivery","writing","work","work on","plan","issues","shipping","code","run","tasks","debugging","2026-11-10 10:12:30",false,"---\nname: ccpm\ndescription: \"CCPM - spec-driven project management: PRD → Epic → GitHub Issues → parallel agents → shipped code. Use this skill for anything in the software delivery lifecycle: writing a PRD ('write a PRD for X', 'let's plan X', 'scope this out'), parsing a PRD into an epic, decomposing an epic into tasks, syncing to GitHub ('sync the X epic', 'push tasks to github'), starting work on an issue ('start working on issue N', 'let's work on issue N'), analyzing parallel work streams, running standups ('standup', 'run the standup'), checking status ('what's next', 'what's blocked', 'what are we working on'), closing issues, or merging an epic. Use ccpm any time the user is talking about shipping a feature, managing work, or tracking progress — even if they don't say 'ccpm' or 'PRD'. Do NOT use for: debugging code, writing tests, reviewing PRs, or raw GitHub issue\u002FPR operations with no delivery context.\"\n---\n\n# CCPM - Claude Code Project Manager\n\nA spec-driven development workflow: PRD → Epic → GitHub Issues → Parallel Agents → Shipped Code.\n\n## Core Philosophy\n\nRequirements live in files, not heads. Every feature starts as a PRD, becomes a technical epic, decomposes into GitHub issues, and gets executed by parallel agents with full traceability.\n\n## File Conventions\n\nBefore doing anything, read `references\u002Fconventions.md` for path standards, frontmatter schemas, and GitHub operation rules. These apply to all phases.\n\n## The Five Phases\n\n### 1. Plan — Capture requirements\n**When**: User wants to define a new feature, product requirement, or scope of work.\n**Read**: `references\u002Fplan.md`\n**Covers**: Writing PRDs through guided brainstorming, converting PRDs to technical epics.\n\n### 2. Structure — Break it down\n**When**: An epic exists and needs to be decomposed into concrete tasks.\n**Read**: `references\u002Fstructure.md`\n**Covers**: Epic decomposition into numbered task files with dependencies and parallelization.\n\n### 3. Sync — Push to GitHub\n**When**: Local epic\u002Ftasks need to become GitHub issues, progress needs to be posted as comments, or a bug is found and needs a linked issue created.\n**Read**: `references\u002Fsync.md`\n**Covers**: Epic sync (epic + tasks → GitHub issues), issue sync (progress comments), closing issues\u002Fepics, bug reporting against completed issues.\n\n### 4. Execute — Start building\n**When**: User wants to start working on one or more GitHub issues with parallel agents.\n**Read**: `references\u002Fexecute.md`\n**Covers**: Issue analysis (parallel work stream identification), launching parallel agents, coordinating worktrees.\n\n### 5. Track — Know where things stand\n**When**: User asks for status, standup report, what's blocked, what's next, or needs to validate state.\n**Read**: `references\u002Ftrack.md`\n**Covers**: Status, standup, search, in-progress, next priority, blocked items, validation.\n\n---\n\n## Script-First Rule\n\nFor deterministic operations — anything that reads and reports without needing reasoning — always run the bash script directly rather than doing the work manually:\n\n| What the user wants | Script to run |\n|---|---|\n| Project status | `bash references\u002Fscripts\u002Fstatus.sh` |\n| Standup report | `bash references\u002Fscripts\u002Fstandup.sh` |\n| List all epics | `bash references\u002Fscripts\u002Fepic-list.sh` |\n| Show epic details | `bash references\u002Fscripts\u002Fepic-show.sh \u003Cname>` |\n| Epic status | `bash references\u002Fscripts\u002Fepic-status.sh \u003Cname>` |\n| List PRDs | `bash references\u002Fscripts\u002Fprd-list.sh` |\n| PRD status | `bash references\u002Fscripts\u002Fprd-status.sh` |\n| Search issues\u002Ftasks | `bash references\u002Fscripts\u002Fsearch.sh \u003Cquery>` |\n| What's in progress | `bash references\u002Fscripts\u002Fin-progress.sh` |\n| What's next | `bash references\u002Fscripts\u002Fnext.sh` |\n| What's blocked | `bash references\u002Fscripts\u002Fblocked.sh` |\n| Validate project state | `bash references\u002Fscripts\u002Fvalidate.sh` |\n\nUse the LLM for work that requires reasoning: writing PRDs, analyzing parallelism, launching agents, synthesizing updates.\n\n---\n\n## Quick Reference\n\n```\nPlan a feature:     \"I want to build X\" or \"create a PRD for X\"\nParse to epic:      \"turn the X PRD into an epic\"\nDecompose:          \"break down the X epic into tasks\"\nSync to GitHub:     \"push the X epic to GitHub\"\nStart an issue:     \"start working on issue 42\"\nCheck status:       \"what's our status\" \u002F \"standup\"\nWhat's next:        \"what should I work on next\"\nMerge epic:         \"merge the X epic\"\nReport a bug:       \"found a bug in issue 42\" \u002F \"testing issue 42 revealed X\"\n```\n","# CCPM - Claude Code Project Manager\n\nA spec-driven development workflow: PRD → Epic → GitHub Issues → Parallel Agents → Shipped Code.\n\n## Core Philosophy\n\nRequirements live in files, not heads. Every feature starts as a PRD, becomes a technical epic, decomposes into GitHub issues, and gets executed by parallel agents with full traceability.\n\n## File Conventions\n\nBefore doing anything, read `references\u002Fconventions.md` for path standards, frontmatter schemas, and GitHub operation rules. These apply to all phases.\n\n## The Five Phases\n\n### 1. Plan — Capture requirements\n**When**: User wants to define a new feature, product requirement, or scope of work.\n**Read**: `references\u002Fplan.md`\n**Covers**: Writing PRDs through guided brainstorming, converting PRDs to technical epics.\n\n### 2. Structure — Break it down\n**When**: An epic exists and needs to be decomposed into concrete tasks.\n**Read**: `references\u002Fstructure.md`\n**Covers**: Epic decomposition into numbered task files with dependencies and parallelization.\n\n### 3. Sync — Push to GitHub\n**When**: Local epic\u002Ftasks need to become GitHub issues, progress needs to be posted as comments, or a bug is found and needs a linked issue created.\n**Read**: `references\u002Fsync.md`\n**Covers**: Epic sync (epic + tasks → GitHub issues), issue sync (progress comments), closing issues\u002Fepics, bug reporting against completed issues.\n\n### 4. Execute — Start building\n**When**: User wants to start working on one or more GitHub issues with parallel agents.\n**Read**: `references\u002Fexecute.md`\n**Covers**: Issue analysis (parallel work stream identification), launching parallel agents, coordinating worktrees.\n\n### 5. Track — Know where things stand\n**When**: User asks for status, standup report, what's blocked, what's next, or needs to validate state.\n**Read**: `references\u002Ftrack.md`\n**Covers**: Status, standup, search, in-progress, next priority, blocked items, validation.\n\n---\n\n## Script-First Rule\n\nFor deterministic operations — anything that reads and reports without needing reasoning — always run the bash script directly rather than doing the work manually:\n\n| What the user wants | Script to run |\n|---|---|\n| Project status | `bash references\u002Fscripts\u002Fstatus.sh` |\n| Standup report | `bash references\u002Fscripts\u002Fstandup.sh` |\n| List all epics | `bash references\u002Fscripts\u002Fepic-list.sh` |\n| Show epic details | `bash references\u002Fscripts\u002Fepic-show.sh \u003Cname>` |\n| Epic status | `bash references\u002Fscripts\u002Fepic-status.sh \u003Cname>` |\n| List PRDs | `bash references\u002Fscripts\u002Fprd-list.sh` |\n| PRD status | `bash references\u002Fscripts\u002Fprd-status.sh` |\n| Search issues\u002Ftasks | `bash references\u002Fscripts\u002Fsearch.sh \u003Cquery>` |\n| What's in progress | `bash references\u002Fscripts\u002Fin-progress.sh` |\n| What's next | `bash references\u002Fscripts\u002Fnext.sh` |\n| What's blocked | `bash references\u002Fscripts\u002Fblocked.sh` |\n| Validate project state | `bash references\u002Fscripts\u002Fvalidate.sh` |\n\nUse the LLM for work that requires reasoning: writing PRDs, analyzing parallelism, launching agents, synthesizing updates.\n\n---\n\n## Quick Reference\n\n```\nPlan a feature:     \"I want to build X\" or \"create a PRD for X\"\nParse to epic:      \"turn the X PRD into an epic\"\nDecompose:          \"break down the X epic into tasks\"\nSync to GitHub:     \"push the X epic to GitHub\"\nStart an issue:     \"start working on issue 42\"\nCheck status:       \"what's our status\" \u002F \"standup\"\nWhat's next:        \"what should I work on next\"\nMerge epic:         \"merge the X epic\"\nReport a bug:       \"found a bug in issue 42\" \u002F \"testing issue 42 revealed X\"\n```\n",{"name":5,"description":7},"main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","manage-project\u002Fautomazeio\u002Fccpm",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill ccpm",{"tool":61,"command":62},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill ccpm",{"tool":64,"command":65},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill ccpm","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002FSKILL.md",true,[69,75,79,83,89,93,97,101,105,109,113,117,121,125,129,133,137,141,145,149],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fconventions.md","REFERENCE","参考文档",4529,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fconventions.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fexecute.md",6386,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fexecute.md",{"path":80,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fplan.md",3087,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fplan.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fscripts\u002Fblocked.sh","SCRIPT","脚本",1791,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fblocked.sh",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fscripts\u002Fepic-list.sh",2514,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fepic-list.sh",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fscripts\u002Fepic-show.sh",2465,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fepic-show.sh",{"path":98,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fscripts\u002Fepic-status.sh",2244,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fepic-status.sh",{"path":102,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fscripts\u002Fhelp.sh",3174,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fhelp.sh",{"path":106,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fscripts\u002Fin-progress.sh",2148,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fin-progress.sh",{"path":110,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fscripts\u002Finit.sh",6112,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Finit.sh",{"path":114,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fscripts\u002Fnext.sh",1698,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fnext.sh",{"path":118,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fscripts\u002Fprd-list.sh",2717,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fprd-list.sh",{"path":122,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fscripts\u002Fprd-status.sh",1704,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fprd-status.sh",{"path":126,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fscripts\u002Fsearch.sh",1650,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fsearch.sh",{"path":130,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fscripts\u002Fstandup.sh",3094,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fstandup.sh",{"path":134,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Fscripts\u002Fstatus.sh",1059,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fstatus.sh",{"path":138,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Fscripts\u002Fvalidate.sh",2713,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fscripts\u002Fvalidate.sh",{"path":142,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":143,"sourceHtmlUrl":144},"references\u002Fstructure.md",3010,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fstructure.md",{"path":146,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":147,"sourceHtmlUrl":148},"references\u002Fsync.md",7712,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Fsync.md",{"path":150,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":151,"sourceHtmlUrl":152},"references\u002Ftrack.md",3240,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmanage-project\u002Fautomazeio\u002Fccpm\u002Freferences\u002Ftrack.md",[154,188,201,221,242,268],{"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":168,"publishedAt":43},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[160,165],{"categoryNo":161,"categoryName":162,"taxonomyType":163,"taxonomyTypeDesc":164},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[169,33,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185,186,187],"writing clearly and concisely","concisely","text","for","more","timeless","error","professional","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":43},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[195,196,33,197,198,179,30,199,200],"crafting effective readmes","README","templates","type","guidance","files",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":210,"publishedAt":43},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源",[211,212,213,214,215,216,217,218,219,220,186],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":227,"publishedAt":43},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[196,228,229,230,215,231,232,30,233,234,48,235,236,237,238,239,186,240,241],"project documentation","tree","kind","expert","github","wish","writer","goal","write","technical writer","technical","https","write a readme","safe",{"skillNo":243,"name":244,"nameZh":6,"description":245,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":246,"categories":247,"keywords":248,"publishedAt":43},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[249,250,179,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":269,"name":270,"nameZh":6,"description":271,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":272,"categories":273,"keywords":276,"publishedAt":43},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[274,275],{"categoryNo":161,"categoryName":162,"taxonomyType":163,"taxonomyTypeDesc":164},{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},[277,278,261,238,33,279,176,280,281,282,283,284,285,286,287,183,288,289,187,290],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]