Synthesize architecture, security, and HLD artifacts into a DevOps plan.
npx skills add https://github.com/gleeb/ai-registry --skill planning-devops
Please help me install this Agent Skill. Skill: planning-devops Source: https://github.com/gleeb/ai-registry/tree/main/systems/sdlc/skills/planning-devops Command: npx skills add https://github.com/gleeb/ai-registry --skill planning-devops
It turns cross-cutting architecture, security, and per-story design outputs into an actionable DevOps plan that teams can execute consistently across environments.
Use the planning-devops skill to draft your Phase 4 DevOps plan and write it to plan/cross-cutting/devops.md based on the existing system architecture, security overview, PRD NFRs, and all completed per-story HLD artifacts.
High-intent search queries and answers about installing and using this skill.
A DevOps deployment plan synthesizes system architecture, security infrastructure requirements, PRD NFRs, and per-story HLD artifacts into a unified CI/CD and operations document. It consolidates cross-cutting design outputs into actionable pipeline stages, environment management strategies, and observability requirements for consistent execution.
Cross-cutting DevOps planning in SDLC Phase 4 converts per-story high-level designs and non-functional requirements into deployment, CI/CD, and operations decisions. It unifies fragmented architecture and security outputs into a single consolidated plan for consistent team execution.
Planning CI/CD pipeline stages and deployment rollback strategy requires synthesizing system architecture and security requirements into a structured workflow. This workflow designs pipeline gates, defines environment management, specifies observability, and validates inputs using REQUIRE/DENY/ALLOW contract terms to ensure operational safety.
Yes, completed per-story HLD artifacts from Phase 3 planning are required before planning DevOps infrastructure. The DevOps planning process dispatches in Phase 4 and synthesizes these per-story designs alongside system architecture, security overviews, and PRD NFRs into the final deployment plan.
A key limitation is strict dependency on completed Phase 3 per-story HLD artifacts, system architecture, and PRD NFRs. The planning workflow enforces REQUIRE/DENY/ALLOW validation gates that prevent premature implementation if inputs are missing or security threats are misplaced, blocking plan generation until resolved.
curdxValidate PRD, UX, architecture, epics, and stories for implementation readiness.
yuhle-qugDesign CI/CD pipelines, containerization, and infrastructure as code with Kubernetes, Docker, and Terraform.
shishiTransform PBIs into ready backlog items with acceptance criteria and dependencies.
AngelP17Automate CI/CD pipelines, infrastructure provisioning, and deployments across AWS, GCP, and Azure.
