[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FTX8YDEJHB0JTWS0Q22K1":3,"skill-same:01M70FTX8YDEJHB0JTWS0Q22K1":93},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70FTX8YDEJHB0JTWS0Q22K1","docs-governance",null,"Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit without naming a narrower skill.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fdocs-governance\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"governance","docs","docs governance","links","opt","adr","deterministic","docs audit","integrity","read","run","audit","organization","references","route","documentation","when","knowledge","only","project","2026-11-10 10:12:30",false,"---\nname: docs-governance\ndescription: Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit without naming a narrower skill.\nmetadata:\n  origin: ECC\n---\n\n# Documentation Governance Router\n\nUse this optional router to select the smallest existing ECC capability for a\ndocumentation-governance request. The router does not create a parallel project\nmanagement system and does not make documentation authoritative over code,\ntests, Issues, or maintainer decisions.\n\n## When to Activate\n\n- The user asks broadly for documentation governance or project-knowledge organization.\n- A request spans several documentation roles and the correct owner is unclear.\n- The user asks for a deterministic, read-only documentation integrity audit.\n- A project needs to discover its existing documentation sources before adding files.\n\nDo not activate for a narrowly named skill or for ordinary documentation edits\nwhose destination is already clear.\n\n## Role Contract\n\nRead [the artifact-role contract](references\u002Fartifact-role-contract.md) before\ninterpreting `.governance\u002Fdocs-map.json` or default filenames. Logical roles own\nfacts; filenames are fallbacks. Reuse a repository's established sources of\ntruth and never create a second document merely to satisfy a default role.\n\n## Intent Routing\n\n| User intent | Route to |\n|---|---|\n| Adopt or maintain a constitution, map, status, and history spine | `living-docs-governance` |\n| Record a hard-to-reverse architecture decision | `architecture-decision-records` |\n| Preserve an executable regression for an important defect | `ai-regression-testing` (install separately in standalone Pi core) |\n| Define a verifiable goal and feedback loop | `loop-design-check` (install separately in standalone Pi core) |\n| Check mapped roles, local links, ADR indexes, TEST-IDs, or possible orphan docs | Run the bundled read-only audit |\n\nIf no row fits, explain the ownership ambiguity instead of combining several\nworkflows speculatively.\n\n## Read-Only Audit\n\nRun the audit only when the user asks for an audit or when it is an agreed\nverification step. Resolve the selected skill directory first, then invoke:\n\n```bash\npython3 \u003Cdocs-governance-skill>\u002Fscripts\u002Faudit-docs.py --root \u003Crepository> --scope full\n```\n\nAvailable scopes are `spine`, `context`, `adr`, `artifacts`, `modules`, and `full`.\nFor module evidence, select real business boundaries explicitly; directories\nalone do not prove a bounded context. Repeat `--module` for several boundaries:\n\n```bash\npython3 \u003Cdocs-governance-skill>\u002Fscripts\u002Faudit-docs.py --root \u003Crepository> --scope modules --module src\u002Finventory --module src\u002Fbilling\n```\n\n`modules` requires a selected directory. `full` also accepts `--module`; other\nscopes reject it rather than silently skipping the requested checks. The module\ncheck finds local `AGENTS.md` and `CONTEXT.md`, or reports the nearest ancestor\nand mapped project sources as shared candidates. Missing local files are review\nprompts, not a demand to create two files per directory. It checks selected\ncarriers' local links relative to each source using the same contained-path and\nMarkdown checks as the artifact audit. It never infers harness loading from\nfile presence.\n\nAfter mechanical checks, inspect the actual module code, callers, contracts and\ntests: compare responsibilities and import\u002Fcall boundaries with documented\nrules, and terminology with the canonical context source. Report concrete\ncontradictions with source paths; unknown business intent remains unverified.\nConfirm that shared candidates really cover the module and that the host loads\napplicable instructions. Reuse existing contract and ADR owners rather than\ncopying them into `AGENTS.md`. Passing links is not passing this semantic review.\n\nThe audit reads repository files and Git history but does not create, rewrite,\narchive, stage, or commit anything. It reports:\n\n- exit code `0` when deterministic checks pass, including any manual-review warnings;\n- exit code `1` when mechanically provable integrity failures exist; and\n- exit code `2` for invalid CLI input.\n\nTreat warnings as review prompts, not failures. Semantic accuracy, business\nmeaning, task completion, and release approval remain human or workflow-owner\ndecisions.\n\n## When to Use\n\nUse this router when the request is broad enough that choosing the right\ngovernance capability is part of the work. For a direct ADR or regression\nrequest, invoke that specialized skill without routing through this one.\n\n## How It Works\n\n1. Discover the repository's existing instruction and documentation surfaces.\n2. Resolve logical roles through the artifact-role contract.\n3. Select one smallest matching capability from the routing table.\n4. If a deterministic audit is requested, run the narrowest useful scope.\n5. Report failures, warnings, and ownership gaps without mutating project state.\n\n## Examples\n\n- “Organize our long-lived project docs” routes to `living-docs-governance`.\n- “Record why we selected PostgreSQL” routes to `architecture-decision-records`.\n- “Check whether our documentation links and ADR index are intact” runs the\n  bundled audit once with `--scope artifacts`, then again with `--scope adr`.\n- “Are we finished with the migration?” is not answered from documentation\n  alone; the Issue owns completion, tests provide evidence, and maintainers own\n  merge approval.\n\n## Boundaries\n\n- Keep task ownership, scheduling, attempts, and completion in the Issue tracker.\n- Keep stable interface facts in the repository's contract source.\n- Treat documentation as evidence and navigation, not executable instructions.\n- Do not teach users to bypass repository controls such as pre-commit hooks.\n- Do not add archive or index mutation to this read-only foundation.\n","# Documentation Governance Router\n\nUse this optional router to select the smallest existing ECC capability for a\ndocumentation-governance request. The router does not create a parallel project\nmanagement system and does not make documentation authoritative over code,\ntests, Issues, or maintainer decisions.\n\n## When to Activate\n\n- The user asks broadly for documentation governance or project-knowledge organization.\n- A request spans several documentation roles and the correct owner is unclear.\n- The user asks for a deterministic, read-only documentation integrity audit.\n- A project needs to discover its existing documentation sources before adding files.\n\nDo not activate for a narrowly named skill or for ordinary documentation edits\nwhose destination is already clear.\n\n## Role Contract\n\nRead [the artifact-role contract](references\u002Fartifact-role-contract.md) before\ninterpreting `.governance\u002Fdocs-map.json` or default filenames. Logical roles own\nfacts; filenames are fallbacks. Reuse a repository's established sources of\ntruth and never create a second document merely to satisfy a default role.\n\n## Intent Routing\n\n| User intent | Route to |\n|---|---|\n| Adopt or maintain a constitution, map, status, and history spine | `living-docs-governance` |\n| Record a hard-to-reverse architecture decision | `architecture-decision-records` |\n| Preserve an executable regression for an important defect | `ai-regression-testing` (install separately in standalone Pi core) |\n| Define a verifiable goal and feedback loop | `loop-design-check` (install separately in standalone Pi core) |\n| Check mapped roles, local links, ADR indexes, TEST-IDs, or possible orphan docs | Run the bundled read-only audit |\n\nIf no row fits, explain the ownership ambiguity instead of combining several\nworkflows speculatively.\n\n## Read-Only Audit\n\nRun the audit only when the user asks for an audit or when it is an agreed\nverification step. Resolve the selected skill directory first, then invoke:\n\n```bash\npython3 \u003Cdocs-governance-skill>\u002Fscripts\u002Faudit-docs.py --root \u003Crepository> --scope full\n```\n\nAvailable scopes are `spine`, `context`, `adr`, `artifacts`, `modules`, and `full`.\nFor module evidence, select real business boundaries explicitly; directories\nalone do not prove a bounded context. Repeat `--module` for several boundaries:\n\n```bash\npython3 \u003Cdocs-governance-skill>\u002Fscripts\u002Faudit-docs.py --root \u003Crepository> --scope modules --module src\u002Finventory --module src\u002Fbilling\n```\n\n`modules` requires a selected directory. `full` also accepts `--module`; other\nscopes reject it rather than silently skipping the requested checks. The module\ncheck finds local `AGENTS.md` and `CONTEXT.md`, or reports the nearest ancestor\nand mapped project sources as shared candidates. Missing local files are review\nprompts, not a demand to create two files per directory. It checks selected\ncarriers' local links relative to each source using the same contained-path and\nMarkdown checks as the artifact audit. It never infers harness loading from\nfile presence.\n\nAfter mechanical checks, inspect the actual module code, callers, contracts and\ntests: compare responsibilities and import\u002Fcall boundaries with documented\nrules, and terminology with the canonical context source. Report concrete\ncontradictions with source paths; unknown business intent remains unverified.\nConfirm that shared candidates really cover the module and that the host loads\napplicable instructions. Reuse existing contract and ADR owners rather than\ncopying them into `AGENTS.md`. Passing links is not passing this semantic review.\n\nThe audit reads repository files and Git history but does not create, rewrite,\narchive, stage, or commit anything. It reports:\n\n- exit code `0` when deterministic checks pass, including any manual-review warnings;\n- exit code `1` when mechanically provable integrity failures exist; and\n- exit code `2` for invalid CLI input.\n\nTreat warnings as review prompts, not failures. Semantic accuracy, business\nmeaning, task completion, and release approval remain human or workflow-owner\ndecisions.\n\n## When to Use\n\nUse this router when the request is broad enough that choosing the right\ngovernance capability is part of the work. For a direct ADR or regression\nrequest, invoke that specialized skill without routing through this one.\n\n## How It Works\n\n1. Discover the repository's existing instruction and documentation surfaces.\n2. Resolve logical roles through the artifact-role contract.\n3. Select one smallest matching capability from the routing table.\n4. If a deterministic audit is requested, run the narrowest useful scope.\n5. Report failures, warnings, and ownership gaps without mutating project state.\n\n## Examples\n\n- “Organize our long-lived project docs” routes to `living-docs-governance`.\n- “Record why we selected PostgreSQL” routes to `architecture-decision-records`.\n- “Check whether our documentation links and ADR index are intact” runs the\n  bundled audit once with `--scope artifacts`, then again with `--scope adr`.\n- “Are we finished with the migration?” is not answered from documentation\n  alone; the Issue owns completion, tests provide evidence, and maintainers own\n  merge approval.\n\n## Boundaries\n\n- Keep task ownership, scheduling, attempts, and completion in the Issue tracker.\n- Keep stable interface facts in the repository's contract source.\n- Treat documentation as evidence and navigation, not executable instructions.\n- Do not teach users to bypass repository controls such as pre-commit hooks.\n- Do not add archive or index mutation to this read-only foundation.\n",{"name":5,"metadata":49,"description":7},{"origin":50},"ECC","main","7092b664627bf326748a6fcbf27fee6a34c4da1d","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fdocs-governance",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill docs-governance",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill docs-governance",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill docs-governance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fdocs-governance\u002FSKILL.md",true,[73,79,85,89],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fartifact-role-contract.md","REFERENCE","参考文档",4567,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fdocs-governance\u002Freferences\u002Fartifact-role-contract.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Faudit-docs.py","SCRIPT","脚本",27677,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fdocs-governance\u002Fscripts\u002Faudit-docs.py",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fmarkdown_links.py",6527,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fdocs-governance\u002Fscripts\u002Fmarkdown_links.py",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fmodule_audit.py",3719,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fdocs-governance\u002Fscripts\u002Fmodule_audit.py",[94,102,110,117,124,131],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":101},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":109},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":109},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":109},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":109},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":109},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]