[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYQ0HM0CGF85BQ1NWEMCHR":3,"skill-same:01M7AYQ0HM0CGF85BQ1NWEMCHR":69},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7AYQ0HM0CGF85BQ1NWEMCHR","md-project-document_templates",null,"Create markdown (.md) project document templates from Body of Knowledge (BOK) standards. Covers BABOK, PMBOK, SWEBOK, SEBOK, CyBOK, DMBOK, UX\u002FUI. Use when building structured project documentation in markdown instead of docx\u002Fxlsx.","oat431\u002Fhermes_config_backup","oat431","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54722120?v=4","01M7AYD07EH8SYPMYY8CGZKS22","Oralita","01M7AYD0816QDF77E3TWCRSQC9",1,"Unlicense","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fmd-project-document-templates\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: md-project-document_templates\ndescription: Create markdown (.md) project document templates from Body of Knowledge (BOK) standards. Covers BABOK, PMBOK, SWEBOK, SEBOK, CyBOK, DMBOK, UX\u002FUI. Use when building structured project documentation in markdown instead of docx\u002Fxlsx.\ntriggers:\n  - project document template\n  - markdown template\n  - BOK document\n  - business case template\n  - SRS template\n  - project charter template\n  - essential documents\n---\n\n# Markdown Project Document Templates\n\n## When to Use\n\nWhen the user asks to create project document templates in `.md` format — business cases, requirements specs, architecture docs, test plans, etc. — sourced from Body of Knowledge standards.\n\n## Workflow\n\n### 1. Understand the Source\n\n- Identify which BOK(s) the document belongs to (BABOK, PMBOK, SWEBOK, SEBOK, CyBOK, DMBOK, UX\u002FUI)\n- Check if a checklist exists (e.g., `TEMPLATE-CHECKLIST.md`) — read it to understand context and dependencies\n- Read the BOK source file for the specific document's definition, priority, and ISO\u002FIEEE references\n\n### 2. Research (if needed)\n\n- Web search for best-practice structures, industry templates, standard sections\n- Cross-reference multiple BOKs — many documents appear in several (e.g., Risk Register in PMBOK + SEBOK)\n- Note which BOKs define the document for traceability\n\n### 3. Template Structure\n\nEvery template MUST include:\n\n**YAML Frontmatter:**\n```yaml\n---\ndocument_type: [Name]\nversion: \"1.0\"\nstatus: Draft\nauthor: \"[Author Name]\"\ncreated: \"[YYYY-MM-DD]\"\nlast_updated: \"[YYYY-MM-DD]\"\nproject_name: \"[Project Name]\"\nproject_id: \"[Project-ID]\"\nclassification: \"Internal \u002F Confidential\"\ntags: [relevant, tags]\nstandard_ref:\n  - BABOK v3 — [Section]\n  - ISO\u002FIEC\u002FIEEE XXXXX — [Title]\n---\n```\n\n**Document Control Block:**\n- Revision History table (Version, Date, Author, Change Description)\n- Approvals table (Role, Name, Signature, Date)\n\n**Table of Contents:**\n- Linked section headers\n\n**Body Sections:**\n- Use tables as primary layout for structured data\n- Use `[placeholder brackets]` for all fill-in values\n- Include emoji priority indicators (🔴 Must Have, 🟡 Nice to Have, 🟢 Optional)\n- Add `> blockquote` guidance notes where users need context\n\n**Related Documents:**\n- `[[Hyphenated-Name]]` cross-references to related templates (NEVER spaces — `[[Business-Case]]` not `[[Business Case]]`)\n\n**Footer:**\n- Template Standard reference (BOK + ISO\u002FIEEE)\n- Usage guidance\n\n### 4. Diagram Rules (CRITICAL)\n\n**ALWAYS use Mermaid for:**\n- Flowcharts, process flows, decision trees\n- Dependency diagrams, architecture diagrams\n- Gantt charts, timelines\n- Journey maps, quadrant charts, mind maps\n- Org charts\n\n**ALWAYS use emoji tables for:**\n- Risk heat maps (not ASCII art)\n- Priority matrices\n- Status dashboards\n- Any grid\u002Fmatrix visualization\n\n**NEVER use ASCII art for any visualization.** User explicitly rejected ASCII in favor of Mermaid and emoji tables.\n\n**Mermaid styling:** Add `style` directives with colors for visual distinction. Use hex colors with `color:#fff` for text.\n\n**Emoji heat map format:**\n```markdown\n| Impact \\ Probability | Low | Medium | High |\n|---------------------|-----|--------|------|\n| **High** | 🟡 | 🟠 | 🔴 |\n| **Medium** | 🟢 | 🟡 | 🟠 |\n| **Low** | 🟢 | 🟢 | 🟡 |\n\n> **Legend:** 🔴 Critical | 🟠 High | 🟡 Medium | 🟢 Low\n```\n\n### 5. Checklist Management\n\nAfter creating a template, update the master checklist:\n- Change `☐` to `✅` for the completed document\n- Use `patch` tool for surgical updates\n\n### 6. Batching\n\n- Default: create 3 templates per batch for user review\n- User reviews before moving to next batch\n- Wait for user confirmation before proceeding\n\n## Common Template Patterns\n\n### Plans (Quality Plan, Risk Plan, etc.)\nSections: Objectives → Scope → Roles\u002FResponsibilities → Processes → Tools → Metrics → Review Cadence\n\n### Reports (Test Report, Audit Report, etc.)\nSections: Executive Summary → Scope → Methodology → Findings → Analysis → Recommendations → Appendices\n\n### Specifications (SRS, API Spec, etc.)\nSections: Overview → Requirements (Functional\u002FNon-Functional) → Constraints → Assumptions → Acceptance Criteria → Traceability\n\n### Registers (Risk Register, Issue Register, etc.)\nSections: Purpose → Classification Scheme → Register Table → Summary\u002FDashboard → Review Process\n\n### Strategies (Change Strategy, Security Strategy, etc.)\nSections: Context → Current State → Options Analysis → Recommendation → Implementation Plan → Governance\n\n## Pitfalls\n\n1. **Broken wikilinks** — Always use hyphens in wikilinks, never spaces. `[[Business-Case]]` not `[[Business Case]]`. Space-separated wikilinks break in Obsidian.\n2. **Don't mix business and technical levels** — Business Requirements describe *what*, SRS describes *how*\n3. **Don't skip the Executive Summary** — busy stakeholders read only this\n4. **Don't forget traceability** — every document should link to related docs via `[[Hyphenated-Name]]` wikilinks\n5. **Don't use vendor-specific language** — templates should be vendor-neutral\n6. **Don't omit the \"Related Documents\" section** — cross-references are critical for the knowledge graph\n7. **Mermaid edge labels with special characters** — Quote labels containing `()`, `\u002F`, `:`, `,`. Example: `A -->|\"1: submit()\"| B`\n8. **Duplicate checklist entries** — Check for duplicate item numbers after each batch update\n\n## Reference Files\n\n- `references\u002Fdiagram-patterns.md` — Mermaid and emoji diagram patterns with color conventions\n- `references\u002Ftemplate-skeleton.md` — Copy-paste YAML frontmatter, document control block, section patterns by doc type\n- `references\u002Fbok-document-mapping.md` — Which documents come from which BOKs, cross-BOK duplicates\n","# Markdown Project Document Templates\n\n## When to Use\n\nWhen the user asks to create project document templates in `.md` format — business cases, requirements specs, architecture docs, test plans, etc. — sourced from Body of Knowledge standards.\n\n## Workflow\n\n### 1. Understand the Source\n\n- Identify which BOK(s) the document belongs to (BABOK, PMBOK, SWEBOK, SEBOK, CyBOK, DMBOK, UX\u002FUI)\n- Check if a checklist exists (e.g., `TEMPLATE-CHECKLIST.md`) — read it to understand context and dependencies\n- Read the BOK source file for the specific document's definition, priority, and ISO\u002FIEEE references\n\n### 2. Research (if needed)\n\n- Web search for best-practice structures, industry templates, standard sections\n- Cross-reference multiple BOKs — many documents appear in several (e.g., Risk Register in PMBOK + SEBOK)\n- Note which BOKs define the document for traceability\n\n### 3. Template Structure\n\nEvery template MUST include:\n\n**YAML Frontmatter:**\n```yaml\n---\ndocument_type: [Name]\nversion: \"1.0\"\nstatus: Draft\nauthor: \"[Author Name]\"\ncreated: \"[YYYY-MM-DD]\"\nlast_updated: \"[YYYY-MM-DD]\"\nproject_name: \"[Project Name]\"\nproject_id: \"[Project-ID]\"\nclassification: \"Internal \u002F Confidential\"\ntags: [relevant, tags]\nstandard_ref:\n  - BABOK v3 — [Section]\n  - ISO\u002FIEC\u002FIEEE XXXXX — [Title]\n---\n```\n\n**Document Control Block:**\n- Revision History table (Version, Date, Author, Change Description)\n- Approvals table (Role, Name, Signature, Date)\n\n**Table of Contents:**\n- Linked section headers\n\n**Body Sections:**\n- Use tables as primary layout for structured data\n- Use `[placeholder brackets]` for all fill-in values\n- Include emoji priority indicators (🔴 Must Have, 🟡 Nice to Have, 🟢 Optional)\n- Add `> blockquote` guidance notes where users need context\n\n**Related Documents:**\n- `[[Hyphenated-Name]]` cross-references to related templates (NEVER spaces — `[[Business-Case]]` not `[[Business Case]]`)\n\n**Footer:**\n- Template Standard reference (BOK + ISO\u002FIEEE)\n- Usage guidance\n\n### 4. Diagram Rules (CRITICAL)\n\n**ALWAYS use Mermaid for:**\n- Flowcharts, process flows, decision trees\n- Dependency diagrams, architecture diagrams\n- Gantt charts, timelines\n- Journey maps, quadrant charts, mind maps\n- Org charts\n\n**ALWAYS use emoji tables for:**\n- Risk heat maps (not ASCII art)\n- Priority matrices\n- Status dashboards\n- Any grid\u002Fmatrix visualization\n\n**NEVER use ASCII art for any visualization.** User explicitly rejected ASCII in favor of Mermaid and emoji tables.\n\n**Mermaid styling:** Add `style` directives with colors for visual distinction. Use hex colors with `color:#fff` for text.\n\n**Emoji heat map format:**\n```markdown\n| Impact \\ Probability | Low | Medium | High |\n|---------------------|-----|--------|------|\n| **High** | 🟡 | 🟠 | 🔴 |\n| **Medium** | 🟢 | 🟡 | 🟠 |\n| **Low** | 🟢 | 🟢 | 🟡 |\n\n> **Legend:** 🔴 Critical | 🟠 High | 🟡 Medium | 🟢 Low\n```\n\n### 5. Checklist Management\n\nAfter creating a template, update the master checklist:\n- Change `☐` to `✅` for the completed document\n- Use `patch` tool for surgical updates\n\n### 6. Batching\n\n- Default: create 3 templates per batch for user review\n- User reviews before moving to next batch\n- Wait for user confirmation before proceeding\n\n## Common Template Patterns\n\n### Plans (Quality Plan, Risk Plan, etc.)\nSections: Objectives → Scope → Roles\u002FResponsibilities → Processes → Tools → Metrics → Review Cadence\n\n### Reports (Test Report, Audit Report, etc.)\nSections: Executive Summary → Scope → Methodology → Findings → Analysis → Recommendations → Appendices\n\n### Specifications (SRS, API Spec, etc.)\nSections: Overview → Requirements (Functional\u002FNon-Functional) → Constraints → Assumptions → Acceptance Criteria → Traceability\n\n### Registers (Risk Register, Issue Register, etc.)\nSections: Purpose → Classification Scheme → Register Table → Summary\u002FDashboard → Review Process\n\n### Strategies (Change Strategy, Security Strategy, etc.)\nSections: Context → Current State → Options Analysis → Recommendation → Implementation Plan → Governance\n\n## Pitfalls\n\n1. **Broken wikilinks** — Always use hyphens in wikilinks, never spaces. `[[Business-Case]]` not `[[Business Case]]`. Space-separated wikilinks break in Obsidian.\n2. **Don't mix business and technical levels** — Business Requirements describe *what*, SRS describes *how*\n3. **Don't skip the Executive Summary** — busy stakeholders read only this\n4. **Don't forget traceability** — every document should link to related docs via `[[Hyphenated-Name]]` wikilinks\n5. **Don't use vendor-specific language** — templates should be vendor-neutral\n6. **Don't omit the \"Related Documents\" section** — cross-references are critical for the knowledge graph\n7. **Mermaid edge labels with special characters** — Quote labels containing `()`, `\u002F`, `:`, `,`. Example: `A -->|\"1: submit()\"| B`\n8. **Duplicate checklist entries** — Check for duplicate item numbers after each batch update\n\n## Reference Files\n\n- `references\u002Fdiagram-patterns.md` — Mermaid and emoji diagram patterns with color conventions\n- `references\u002Ftemplate-skeleton.md` — Copy-paste YAML frontmatter, document control block, section patterns by doc type\n- `references\u002Fbok-document-mapping.md` — Which documents come from which BOKs, cross-BOK duplicates\n",{"name":5,"triggers":24,"description":7},[25,26,27,28,29,30,31],"project document template","markdown template","BOK document","business case template","SRS template","project charter template","essential documents","main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Fhermes-main-profile\u002Fmd-project-document-templates",0,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup","https:\u002F\u002Fgithub.com\u002Foat431","https:\u002F\u002Fpanomete.com\u002F","Hope and Luck is not a part of the strategy, \r\n\r\nSoftskill produces plan Hard skill produce product.","2026-11-03 00:43:08",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add oat431\u002Fhermes_config_backup --skill md-project-document_templates",{"tool":47,"command":48},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill md-project-document_templates",{"tool":50,"command":51},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill md-project-document_templates","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fmd-project-document-templates\u002FSKILL.md",true,[55,61,65],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fbok-document-mapping.md","REFERENCE","参考文档",3386,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fmd-project-document-templates\u002Freferences\u002Fbok-document-mapping.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fdiagram-patterns.md",2635,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fmd-project-document-templates\u002Freferences\u002Fdiagram-patterns.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Ftemplate-skeleton.md",2364,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fhermes-main-profile\u002Fmd-project-document-templates\u002Freferences\u002Ftemplate-skeleton.md",[70,78,85,92,99,106],{"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":74,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7AYZ2JY3NFKAPQSC39N5F3F","project-spec-docs","Fill\u002Fupdate project_spec docs (templates, MM handoffs).","MIT","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fproject-spec-docs\u002FSKILL.md",[],[],{"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":74,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7AYYRZPE7HQX7778558X52S","penpot-mcp","Penpot MCP: connect, verify, and fix streaming via nginx.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fpenpot-mcp\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AYYNKP61CN2281VMJDXMB5","nginx-streaming-proxy","Configure nginx for streaming endpoints (SSE, MCP, WS).","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fnginx-streaming-proxy\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7AYYJP0MDV1D3WVEEZB3SGA","branding-ci","Use for brand\u002FCI identity, style guides, and brand docs.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fui-ux\u002Fbranding-ci\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AYYGCXVT97DDTCM0ZJT6F6","yuanbao","Yuanbao (元宝) groups: @mention users, query info\u002Fmembers.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fyuanbao\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7AYYC2Y65NMGMD4GQXAZMMS","slidev","Create and present web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, and interactive features. Use when building technical presentations, conference talks, code walkthroughs, teaching materials, or developer decks.","https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fshared-skills\u002Fslidev\u002FSKILL.md",[],[]]