[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AYEMJD5YTFYMWFTQ91HT3G":3,"skill-same:01M7AYEMJD5YTFYMWFTQ91HT3G":67},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7AYEMJD5YTFYMWFTQ91HT3G","devops-doc-authoring",null,"Produce DevOps document suites (CI\u002FCD, deployment plan, release notes, runbook) from project specs and templates. Reads upstream docs (architecture, API spec, build scripts, dependency manifests, test plan) to extract deployment-relevant details, then tailors templates to the project's actual infrastructure.","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\u002Fdevops\u002Fdevops-doc-authoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: devops-doc-authoring\ndescription: >\n  Produce DevOps document suites (CI\u002FCD, deployment plan, release notes, runbook)\n  from project specs and templates. Reads upstream docs (architecture, API spec,\n  build scripts, dependency manifests, test plan) to extract deployment-relevant\n  details, then tailors templates to the project's actual infrastructure.\ntrigger: >\n  User asks to create\u002Ffill DevOps docs (05_devops folder), deployment documentation,\n  CI\u002FCD config, runbook, or release notes for a project that already has spec docs\n  (01–04 phases). Also triggers when user says \"fill the devops template\" or\n  \"create the operations docs.\"\n---\n\n# DevOps Document Authoring\n\nProduce a complete `05_devops\u002F` document suite by reading upstream project specs\nand tailoring standard templates to the project's actual architecture.\n\n## When to Use\n\n- User has a project with existing spec docs (01_requirement, 02_design, 03_construction, 04_testing)\n- User wants the DevOps phase documents created\n- User asks to audit, assess, or improve an existing release\u002Fdeployment checklist or DevOps document\n- User asks whether a release checklist is ready for production, enterprise, or full-scale use\n- Templates exist at a known template path\n\n## Prerequisites\n\nBefore writing any document, read ALL of these upstream sources:\n\n| Source Folder | Key Files to Read | What to Extract |\n|--------------|-------------------|-----------------|\n| `01_requirement\u002F` | `011_business_objective.md` | Project name, ID, tech stack, stakeholders, KPIs |\n| `02_design\u002F` | `025_software_architecture_document.md` | Architecture style, deployment topology, ports, network, security model |\n| `02_design\u002F` | `029_architecture_overview.md` | Component map, port map, tech stack summary |\n| `02_design\u002F` | `022_API_specification.md` | Endpoints, rate limits, auth, CORS |\n| `02_design\u002F` | `023_database_schema_DDL.md` | Tables, extensions, triggers, migrations |\n| `03_construction\u002F` | `031_BE_README.md` + `031_FE_README.md` | Build commands, Docker setup, project structure |\n| `03_construction\u002F` | `032_BE_build_scripts.md` + `032_FE_build_scripts.md` | Makefile targets, Dockerfile stages, npm scripts |\n| `03_construction\u002F` | `033_BE_dependency_manifest.md` + `033_FE_dependency_manifest.md` | Key dependencies, versions, licenses |\n| `03_construction\u002F` | `034_SHARED_commit_messages_changelog.md` | Commit convention, scopes, changelog format |\n| `04_testing\u002F` | `041_test_plan.md` | Test levels, tools, environments, entry\u002Fexit criteria |\n\n## Workflow\n\n### Existing DevOps \u002F Release Checklist Audit\n\nWhen auditing an existing release or deployment checklist, distinguish two questions:\n\n1. **Lifecycle coverage:** Does it cover versioning, build, promotion, migration, rollout, verification, rollback, communication, and review?\n2. **Release-gate maturity:** Does it require evidence, artifact identity, approvals, risk decisions, health thresholds, recovery choices, and an auditable closeout?\n\nDo not label a checklist merely as a “low-risk checklist” because it lacks mature gate mechanics. State clearly whether it is a strong full-lifecycle baseline, a sufficient standalone production gate, or suitable for regulated\u002Fmission-critical use. If it already covers the lifecycle, recommend improving the canonical checklist with risk overlays and evidence rather than creating a separate low-risk checklist.\n\nAudit workflow:\n\n1. Read the target checklist and all linked\u002Fdomain checklists.\n2. Inspect internal links and sibling notes for naming and ownership consistency.\n3. Audit artifact identity: release\u002Fversion, commit SHA, build ID, artifact digest, SBOM, signature, provenance, and build-once\u002Fpromote-same-artifact.\n4. Audit operational controls: deployment strategy, exposure strategy, health model, promotion\u002Fabort criteria, observation window, rollback\u002Fforward-fix, and handoff.\n5. Audit stateful changes: schema compatibility, migration locking\u002Fbackfill, data validation, and explicit restore\u002Fforward-fix decisions.\n6. Audit risk scoping: do not let user count or “POC\u002Finternal” labels override internet exposure, sensitive data, production credentials, business criticality, RTO\u002FRPO, regulation, or blast radius.\n7. Check for platform assumptions in documents claiming to be framework-agnostic; move commands into platform-specific runbooks.\n8. Use current authoritative sources when the user asks for a full-scale or best-practice assessment; prefer Google SRE, DORA, SLSA, NIST SSDF, and platform safe-deployment guidance.\n9. Report findings with line references and severity. Do not modify the user’s file during an audit unless explicitly asked.\n\nFor the reusable audit checklist and research notes, see `references\u002Frelease-checklist-audit.md`.\n\n### Microservice Checklist Suite Audit\n\nWhen auditing a microservice checklist folder, exclude implementation-specific overlays (for example, `spring-boot\u002F`) unless the user explicitly includes them. Treat the root notes as a coordinated suite rather than seven unrelated documents.\n\nAudit workflow:\n\n1. Inventory every root note, line count, checklist count, and excluded subfolder; report the exact scope.\n2. Read every in-scope note before judging completeness. Inspect all Obsidian wikilinks and relative Markdown links against the actual vault paths; broken links are release-safety defects because they hide the detailed control.\n3. Establish canonical ownership: the system\u002Finfrastructure checklist should own architecture-level decisions, while gateway, authentication, load balancing, data\u002Fmessaging, observability, and resilience notes own their detailed gates. Flag duplicated rules that can drift.\n4. Reconcile cross-note trust boundaries and guarantees, especially gateway JWT validation versus service-level authorization, JWKS discovery, health-check semantics, retry ownership, fallback safety, and delivery guarantees.\n5. Separate platform-neutral outcomes from platform overlays. Docker Compose, Kubernetes, VM\u002Fsystemd, service mesh, and managed-cloud controls must be conditional or linked overlays, not universal requirements in a framework-agnostic checklist.\n6. Replace absolute rules and arbitrary defaults with a decision field: selected option, rationale, evidence, owner, N\u002FA reason, exception approver, and review\u002Fexpiry date. Examples such as timeout values, replica counts, service-count thresholds, SLOs, and resource sizes are starting points, not universal policy.\n7. Audit security claims against current authoritative guidance: issuer metadata and `jwks_uri`, algorithm allowlists, PKCE, token lifecycle\u002Frevocation, password policy, trusted proxy headers, and defense-in-depth authorization.\n8. Audit messaging claims for delivery semantics, idempotency, outbox\u002Freplay behavior, saga compensation, broker HA\u002Fsecurity\u002Fretention, and the distinction between at-least-once, effectively-once, and true exactly-once boundaries.\n9. Audit observability for metric cardinality, correlation-context availability, telemetry privacy\u002Fretention, alert ownership, and collector failure—not only the presence of logs, metrics, and traces.\n10. Audit resilience for retry amplification, deadline propagation, circuit-breaker applicability, safe versus unsafe fallbacks, backpressure, load shedding, and measurable failure scenarios.\n11. Produce a folder-level verdict plus file-level P1\u002FP2\u002FP3 findings, with line references, concrete corrections, cross-file contradictions, missing controls, and a clear statement that no files were modified unless explicitly requested.\n12. If editing is explicitly approved, apply coordinated changes only to in-scope root notes, then verify frontmatter\u002Fversion, zero unresolved links, no stale relative Markdown links, no leftover contradictory patterns, and unchanged hashes\u002Fsizes for excluded folders.\n\nFor the reusable microservice-suite audit matrix and research anchors, see `references\u002Fmicroservice-checklist-audit.md`.\n\n### Step 1: Context Gathering (Read-Heavy)\n\nRead ALL upstream documents listed above. Do NOT write any DevOps doc until you've\nread the full project context. This is the most important step — skipping it\nproduces generic, templated docs instead of tailored ones.\n\n### Step 2: Extract Deployment-Relevant Facts\n\nFrom the upstream docs, build a mental model of:\n\n- **Components** — what runs where (containers, ports, networks)\n- **Build toolchain** — Go\u002FNode\u002Fetc., Makefile\u002Fnpm, Dockerfile stages\n- **Infrastructure** — Docker\u002FK8s\u002Fserverless, managed services, shared networks\n- **External integrations** — APIs, webhooks, OAuth tokens, third-party services\n- **Security model** — auth mechanisms, secrets management, TLS\n- **Database** — version, extensions, migration tool, backup strategy\n- **Public access** — tunnels, load balancers, CDN, DNS\n\n### Step 3: Read Templates\n\nRead all template files from the template directory (e.g., `template\u002F05_devops\u002F`).\nUnderstand the template structure, section order, and placeholder format.\n\n### Step 4: Author Each Document\n\nProduce all 4 DevOps documents, tailoring every section to the project's reality:\n\n| # | Document | Template | Key Tailoring Points |\n|---|----------|----------|---------------------|\n| 051 | CI\u002FCD Pipeline Configuration | `051_CICD_pipeline_configuration.md` | Workflow YAML matching actual build toolchain, correct service containers for tests, proper image registry, deploy steps matching actual infrastructure |\n| 052 | Deployment Plan | `052_deployment_plan.md` | Actual deploy commands for the target infra, first-time bootstrap guide, rollback procedure using image tags, database migration strategy |\n| 053 | Release Notes | `053_release_notes.md` | Planned features from user stories, conventional commit → section mapping matching the project's commit convention, release history table |\n| 054 | Operations Manual \u002F Runbook | `054_operations_manual_runbook.md` | Actual container names, ports, log commands, troubleshooting tables for the project's specific failure modes, database queries, quick reference card |\n\n### Step 5: Verify\n\nAfter writing, verify the folder structure:\n```\n05_devops\u002F\n├── 051_CICD_pipeline_configuration.md\n├── 052_deployment_plan.md\n├── 053_release_notes.md\n└── 054_operations_manual_runbook.md\n```\n\n## Critical Rules\n\n1. **Never generic.** Every command, port, container name, and URL must match the\n   project's actual architecture. If the project uses Docker Compose on a homelab,\n   don't write Kubernetes commands.\n\n2. **Read before write.** The upstream docs (01–04) are the source of truth. If a\n   detail isn't in the upstream docs, note it as TBD — don't invent it.\n\n3. **Frontmatter must match convention.** Use the same YAML frontmatter structure\n   as all other project docs (document_type, version, status, author, created,\n   last_updated, project_name, project_id, classification, tags, standard_ref,\n   parent_project).\n\n4. **Cross-reference.** Every DevOps doc should link to relevant upstream docs\n   and to sibling DevOps docs via `[[document_name]]` syntax.\n\n5. **Pragmatic over aspirational.** For small projects (1 dev, homelab), don't\n   write Kubernetes manifests or multi-environment promotion pipelines. Match\n   the scale.\n\n6. **Infrastructure = code.** Include actual Docker Compose, Nginx config,\n   GitHub Actions YAML — not pseudocode or placeholders.\n\n7. **Rollback always.** Every deployment doc must include a rollback procedure.\n   Every CI\u002FCD doc must preserve previous image tags.\n\n## Pitfalls\n\n| Pitfall | Why It Happens | Prevention |\n|---------|---------------|------------|\n| Generic CI\u002FCD YAML that doesn't match build toolchain | Didn't read `032_build_scripts.md` | Always read build scripts first |\n| Wrong ports or container names | Assumed defaults instead of reading architecture doc | Extract from `029_architecture_overview.md` port map |\n| Missing `db-network` or shared infrastructure | Didn't check existing homelab setup | Read architecture deployment section carefully |\n| Kubernetes commands for Docker Compose project | Template assumed K8s | Read architecture, then tailor — never blindly copy template |\n| Secrets in committed YAML | Copied from template without redacting | Use `${{ secrets.* }}` in CI, `${VAR}` in Compose |\n| No healthcheck in Docker Compose | Omitted for brevity | Always include healthcheck — it gates deploy verification |\n| Runbook troubleshooting too generic | Didn't think about project-specific failure modes | Read API spec + architecture to identify actual failure scenarios |\n\n## Output Convention\n\nAll documents go in `05_devops\u002F` folder at the same level as the project's\nother spec folders (01_requirement, 02_design, etc.). File naming follows\nthe `05N_document_name.md` pattern from the template directory.\n\n## Support Files\n\n- `references\u002Fhomelab-ghcr-cicd-pattern.md` — Reusable CI\u002FCD YAML patterns for\n  homelab + GHCR + Docker Compose deployments (GitHub Actions workflow, Compose\n  production file, Nginx proxy, rollback commands)\n- `references\u002Fdevops-doc-suite-structure.md` — What each of the 4 DevOps documents\n  must include, who reads it, and how they cross-reference each other\n","# DevOps Document Authoring\n\nProduce a complete `05_devops\u002F` document suite by reading upstream project specs\nand tailoring standard templates to the project's actual architecture.\n\n## When to Use\n\n- User has a project with existing spec docs (01_requirement, 02_design, 03_construction, 04_testing)\n- User wants the DevOps phase documents created\n- User asks to audit, assess, or improve an existing release\u002Fdeployment checklist or DevOps document\n- User asks whether a release checklist is ready for production, enterprise, or full-scale use\n- Templates exist at a known template path\n\n## Prerequisites\n\nBefore writing any document, read ALL of these upstream sources:\n\n| Source Folder | Key Files to Read | What to Extract |\n|--------------|-------------------|-----------------|\n| `01_requirement\u002F` | `011_business_objective.md` | Project name, ID, tech stack, stakeholders, KPIs |\n| `02_design\u002F` | `025_software_architecture_document.md` | Architecture style, deployment topology, ports, network, security model |\n| `02_design\u002F` | `029_architecture_overview.md` | Component map, port map, tech stack summary |\n| `02_design\u002F` | `022_API_specification.md` | Endpoints, rate limits, auth, CORS |\n| `02_design\u002F` | `023_database_schema_DDL.md` | Tables, extensions, triggers, migrations |\n| `03_construction\u002F` | `031_BE_README.md` + `031_FE_README.md` | Build commands, Docker setup, project structure |\n| `03_construction\u002F` | `032_BE_build_scripts.md` + `032_FE_build_scripts.md` | Makefile targets, Dockerfile stages, npm scripts |\n| `03_construction\u002F` | `033_BE_dependency_manifest.md` + `033_FE_dependency_manifest.md` | Key dependencies, versions, licenses |\n| `03_construction\u002F` | `034_SHARED_commit_messages_changelog.md` | Commit convention, scopes, changelog format |\n| `04_testing\u002F` | `041_test_plan.md` | Test levels, tools, environments, entry\u002Fexit criteria |\n\n## Workflow\n\n### Existing DevOps \u002F Release Checklist Audit\n\nWhen auditing an existing release or deployment checklist, distinguish two questions:\n\n1. **Lifecycle coverage:** Does it cover versioning, build, promotion, migration, rollout, verification, rollback, communication, and review?\n2. **Release-gate maturity:** Does it require evidence, artifact identity, approvals, risk decisions, health thresholds, recovery choices, and an auditable closeout?\n\nDo not label a checklist merely as a “low-risk checklist” because it lacks mature gate mechanics. State clearly whether it is a strong full-lifecycle baseline, a sufficient standalone production gate, or suitable for regulated\u002Fmission-critical use. If it already covers the lifecycle, recommend improving the canonical checklist with risk overlays and evidence rather than creating a separate low-risk checklist.\n\nAudit workflow:\n\n1. Read the target checklist and all linked\u002Fdomain checklists.\n2. Inspect internal links and sibling notes for naming and ownership consistency.\n3. Audit artifact identity: release\u002Fversion, commit SHA, build ID, artifact digest, SBOM, signature, provenance, and build-once\u002Fpromote-same-artifact.\n4. Audit operational controls: deployment strategy, exposure strategy, health model, promotion\u002Fabort criteria, observation window, rollback\u002Fforward-fix, and handoff.\n5. Audit stateful changes: schema compatibility, migration locking\u002Fbackfill, data validation, and explicit restore\u002Fforward-fix decisions.\n6. Audit risk scoping: do not let user count or “POC\u002Finternal” labels override internet exposure, sensitive data, production credentials, business criticality, RTO\u002FRPO, regulation, or blast radius.\n7. Check for platform assumptions in documents claiming to be framework-agnostic; move commands into platform-specific runbooks.\n8. Use current authoritative sources when the user asks for a full-scale or best-practice assessment; prefer Google SRE, DORA, SLSA, NIST SSDF, and platform safe-deployment guidance.\n9. Report findings with line references and severity. Do not modify the user’s file during an audit unless explicitly asked.\n\nFor the reusable audit checklist and research notes, see `references\u002Frelease-checklist-audit.md`.\n\n### Microservice Checklist Suite Audit\n\nWhen auditing a microservice checklist folder, exclude implementation-specific overlays (for example, `spring-boot\u002F`) unless the user explicitly includes them. Treat the root notes as a coordinated suite rather than seven unrelated documents.\n\nAudit workflow:\n\n1. Inventory every root note, line count, checklist count, and excluded subfolder; report the exact scope.\n2. Read every in-scope note before judging completeness. Inspect all Obsidian wikilinks and relative Markdown links against the actual vault paths; broken links are release-safety defects because they hide the detailed control.\n3. Establish canonical ownership: the system\u002Finfrastructure checklist should own architecture-level decisions, while gateway, authentication, load balancing, data\u002Fmessaging, observability, and resilience notes own their detailed gates. Flag duplicated rules that can drift.\n4. Reconcile cross-note trust boundaries and guarantees, especially gateway JWT validation versus service-level authorization, JWKS discovery, health-check semantics, retry ownership, fallback safety, and delivery guarantees.\n5. Separate platform-neutral outcomes from platform overlays. Docker Compose, Kubernetes, VM\u002Fsystemd, service mesh, and managed-cloud controls must be conditional or linked overlays, not universal requirements in a framework-agnostic checklist.\n6. Replace absolute rules and arbitrary defaults with a decision field: selected option, rationale, evidence, owner, N\u002FA reason, exception approver, and review\u002Fexpiry date. Examples such as timeout values, replica counts, service-count thresholds, SLOs, and resource sizes are starting points, not universal policy.\n7. Audit security claims against current authoritative guidance: issuer metadata and `jwks_uri`, algorithm allowlists, PKCE, token lifecycle\u002Frevocation, password policy, trusted proxy headers, and defense-in-depth authorization.\n8. Audit messaging claims for delivery semantics, idempotency, outbox\u002Freplay behavior, saga compensation, broker HA\u002Fsecurity\u002Fretention, and the distinction between at-least-once, effectively-once, and true exactly-once boundaries.\n9. Audit observability for metric cardinality, correlation-context availability, telemetry privacy\u002Fretention, alert ownership, and collector failure—not only the presence of logs, metrics, and traces.\n10. Audit resilience for retry amplification, deadline propagation, circuit-breaker applicability, safe versus unsafe fallbacks, backpressure, load shedding, and measurable failure scenarios.\n11. Produce a folder-level verdict plus file-level P1\u002FP2\u002FP3 findings, with line references, concrete corrections, cross-file contradictions, missing controls, and a clear statement that no files were modified unless explicitly requested.\n12. If editing is explicitly approved, apply coordinated changes only to in-scope root notes, then verify frontmatter\u002Fversion, zero unresolved links, no stale relative Markdown links, no leftover contradictory patterns, and unchanged hashes\u002Fsizes for excluded folders.\n\nFor the reusable microservice-suite audit matrix and research anchors, see `references\u002Fmicroservice-checklist-audit.md`.\n\n### Step 1: Context Gathering (Read-Heavy)\n\nRead ALL upstream documents listed above. Do NOT write any DevOps doc until you've\nread the full project context. This is the most important step — skipping it\nproduces generic, templated docs instead of tailored ones.\n\n### Step 2: Extract Deployment-Relevant Facts\n\nFrom the upstream docs, build a mental model of:\n\n- **Components** — what runs where (containers, ports, networks)\n- **Build toolchain** — Go\u002FNode\u002Fetc., Makefile\u002Fnpm, Dockerfile stages\n- **Infrastructure** — Docker\u002FK8s\u002Fserverless, managed services, shared networks\n- **External integrations** — APIs, webhooks, OAuth tokens, third-party services\n- **Security model** — auth mechanisms, secrets management, TLS\n- **Database** — version, extensions, migration tool, backup strategy\n- **Public access** — tunnels, load balancers, CDN, DNS\n\n### Step 3: Read Templates\n\nRead all template files from the template directory (e.g., `template\u002F05_devops\u002F`).\nUnderstand the template structure, section order, and placeholder format.\n\n### Step 4: Author Each Document\n\nProduce all 4 DevOps documents, tailoring every section to the project's reality:\n\n| # | Document | Template | Key Tailoring Points |\n|---|----------|----------|---------------------|\n| 051 | CI\u002FCD Pipeline Configuration | `051_CICD_pipeline_configuration.md` | Workflow YAML matching actual build toolchain, correct service containers for tests, proper image registry, deploy steps matching actual infrastructure |\n| 052 | Deployment Plan | `052_deployment_plan.md` | Actual deploy commands for the target infra, first-time bootstrap guide, rollback procedure using image tags, database migration strategy |\n| 053 | Release Notes | `053_release_notes.md` | Planned features from user stories, conventional commit → section mapping matching the project's commit convention, release history table |\n| 054 | Operations Manual \u002F Runbook | `054_operations_manual_runbook.md` | Actual container names, ports, log commands, troubleshooting tables for the project's specific failure modes, database queries, quick reference card |\n\n### Step 5: Verify\n\nAfter writing, verify the folder structure:\n```\n05_devops\u002F\n├── 051_CICD_pipeline_configuration.md\n├── 052_deployment_plan.md\n├── 053_release_notes.md\n└── 054_operations_manual_runbook.md\n```\n\n## Critical Rules\n\n1. **Never generic.** Every command, port, container name, and URL must match the\n   project's actual architecture. If the project uses Docker Compose on a homelab,\n   don't write Kubernetes commands.\n\n2. **Read before write.** The upstream docs (01–04) are the source of truth. If a\n   detail isn't in the upstream docs, note it as TBD — don't invent it.\n\n3. **Frontmatter must match convention.** Use the same YAML frontmatter structure\n   as all other project docs (document_type, version, status, author, created,\n   last_updated, project_name, project_id, classification, tags, standard_ref,\n   parent_project).\n\n4. **Cross-reference.** Every DevOps doc should link to relevant upstream docs\n   and to sibling DevOps docs via `[[document_name]]` syntax.\n\n5. **Pragmatic over aspirational.** For small projects (1 dev, homelab), don't\n   write Kubernetes manifests or multi-environment promotion pipelines. Match\n   the scale.\n\n6. **Infrastructure = code.** Include actual Docker Compose, Nginx config,\n   GitHub Actions YAML — not pseudocode or placeholders.\n\n7. **Rollback always.** Every deployment doc must include a rollback procedure.\n   Every CI\u002FCD doc must preserve previous image tags.\n\n## Pitfalls\n\n| Pitfall | Why It Happens | Prevention |\n|---------|---------------|------------|\n| Generic CI\u002FCD YAML that doesn't match build toolchain | Didn't read `032_build_scripts.md` | Always read build scripts first |\n| Wrong ports or container names | Assumed defaults instead of reading architecture doc | Extract from `029_architecture_overview.md` port map |\n| Missing `db-network` or shared infrastructure | Didn't check existing homelab setup | Read architecture deployment section carefully |\n| Kubernetes commands for Docker Compose project | Template assumed K8s | Read architecture, then tailor — never blindly copy template |\n| Secrets in committed YAML | Copied from template without redacting | Use `${{ secrets.* }}` in CI, `${VAR}` in Compose |\n| No healthcheck in Docker Compose | Omitted for brevity | Always include healthcheck — it gates deploy verification |\n| Runbook troubleshooting too generic | Didn't think about project-specific failure modes | Read API spec + architecture to identify actual failure scenarios |\n\n## Output Convention\n\nAll documents go in `05_devops\u002F` folder at the same level as the project's\nother spec folders (01_requirement, 02_design, etc.). File naming follows\nthe `05N_document_name.md` pattern from the template directory.\n\n## Support Files\n\n- `references\u002Fhomelab-ghcr-cicd-pattern.md` — Reusable CI\u002FCD YAML patterns for\n  homelab + GHCR + Docker Compose deployments (GitHub Actions workflow, Compose\n  production file, Nginx proxy, rollback commands)\n- `references\u002Fdevops-doc-suite-structure.md` — What each of the 4 DevOps documents\n  must include, who reads it, and how they cross-reference each other\n",{"name":5,"trigger":24,"description":25},"User asks to create\u002Ffill DevOps docs (05_devops folder), deployment documentation, CI\u002FCD config, runbook, or release notes for a project that already has spec docs (01–04 phases). Also triggers when user says \"fill the devops template\" or \"create the operations docs.\"","Produce DevOps document suites (CI\u002FCD, deployment plan, release notes, runbook) from project specs and templates. Reads upstream docs (architecture, API spec, build scripts, dependency manifests, test plan) to extract deployment-relevant details, then tailors templates to the project's actual infrastructure.\n","main","2988869c5a7d7be2225c9ea7a54a4a56a59b0d45","workflow\u002Fdevops\u002Fdevops-doc-authoring",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add oat431\u002Fhermes_config_backup --skill devops-doc-authoring",{"tool":41,"command":42},"bunx","bunx skills add oat431\u002Fhermes_config_backup --skill devops-doc-authoring",{"tool":44,"command":45},"pnpm","pnpm dlx skills add oat431\u002Fhermes_config_backup --skill devops-doc-authoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fdevops\u002Fdevops-doc-authoring\u002FSKILL.md",true,[49,55,59,63],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fdevops-doc-suite-structure.md","REFERENCE","参考文档",3799,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fdevops\u002Fdevops-doc-authoring\u002Freferences\u002Fdevops-doc-suite-structure.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fhomelab-ghcr-cicd-pattern.md",4737,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fdevops\u002Fdevops-doc-authoring\u002Freferences\u002Fhomelab-ghcr-cicd-pattern.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fmicroservice-checklist-audit.md",7928,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fdevops\u002Fdevops-doc-authoring\u002Freferences\u002Fmicroservice-checklist-audit.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Frelease-checklist-audit.md",8109,"https:\u002F\u002Fgithub.com\u002Foat431\u002Fhermes_config_backup\u002Fblob\u002Fmain\u002Fworkflow\u002Fdevops\u002Fdevops-doc-authoring\u002Freferences\u002Frelease-checklist-audit.md",[68,76,83,90,97,104],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"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":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":110,"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",[],[]]