sddp-devops

Define a canonical project-level deployment and operations context in specs/dod.md.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/patrickrmoore/sdd-test --skill sddp-devops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sddp-devops
Source: https://github.com/patrickrmoore/sdd-test/tree/main/.claude/skills/sddp-devops
Command: npx skills add https://github.com/patrickrmoore/sdd-test --skill sddp-devops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or refine the canonical project-level deployment and operations context, focusing on deployment, infrastructure, observability, reliability, and operations rather than feature-specific details.

Core Features & Use Cases

  • Canonical project-level deployment and operations context (specs/dod.md) as a single source of truth for architecture and runbook planning.
  • Guidance for deployment strategies, infrastructure choices, observability plans, and reliability requirements across teams.
  • Seamless governance and collaboration across DevOps, SRE, and Platform teams during project initiation and ongoing refinement.

Quick Start

Create the canonical project-level deployment and operations context for the current project.

Frequently Asked Questions about sddp-devops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a project-level deployment and operations context for my team?

Define a canonical specs/dod.md artifact to establish project-level deployment and operations context, serving as the single source of truth for architecture, deployment strategies, observability, and runbook planning across teams.

What is the best way to align infrastructure decisions with observability and reliability requirements?

Aligning infrastructure decisions requires a canonical deployment and operations context that guides observability planning, reliability requirements, and deployment strategies while maintaining traceable updates to a central specs/dod.md artifact.

When do I need to define a canonical deployment and operations context for my project?

Define a canonical deployment and operations context during project initiation or ongoing refinement to coordinate governance, deployment strategies, and runbook planning across DevOps, SRE, and Platform teams.

Can I use this approach to manage project governance across multiple DevOps and SRE teams?

Yes, this approach enables seamless governance and collaboration across DevOps, SRE, and Platform teams by requiring a well-defined specs/dod.md artifact and maintaining alignment with deployment and operations standards.

Does defining deployment and operations standards require a specific artifact format?

Yes, defining deployment and operations standards specifically requires a well-defined specs/dod.md artifact to ensure traceable updates and serve as the single source of truth for project-level architecture and runbook planning.