prd-v08-release-planning_skill

This skill converts EPICs into production-ready DEP- entries by defining environments, release criteria, rollback triggers, and validation steps.
  • Python

17

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill mattgierhart/prd-driven-context-engineering --skill prd-v08-release-planning

  • SKILL.md7.1 KB

Overview

This skill defines release criteria, deployment environments, and rollback strategies for PRD v0.8 Deployment & Ops. It turns completed EPICs into production-ready DEP- entries that act as a contract between development and operations. Outputs are structured DEP- items covering environment, criteria, rollback, and validation steps.

How this skill works

On request, the skill inventories completed EPICs and related artifacts, then produces DEP- entries using a consistent template. It sets environment-specific configs (staging, preview, production), formalizes pre-deploy blockers and verification steps, and encodes rollback triggers with thresholds and procedures. The result is traceable DEP- documentation ready for runbook and monitoring integration.

When to use it

  • When planning a release or answering “how do we deploy?”
  • Before promoting code from staging to production
  • When defining go/no-go release criteria and owners
  • When creating rollback procedures and alert thresholds
  • When producing post-deploy validation and runbook inputs

Best practices

  • Treat each release as a contract: define environments, criteria, and owners for every DEP- entry
  • Use measurable thresholds for blockers and rollback triggers (error rates, latency, data integrity)
  • Link DEP- entries to EPIC-, TEST-, MON- and API- IDs for traceability
  • Prefer automated verification (CI/CD, smoke tests) and document any manual steps
  • Choose a deployment pattern (canary, blue-green, rolling, feature flags) that matches risk and infra constraints

Example use cases

  • Create DEP- Environment entries for production, staging, and preview with infra, secrets, and access lists
  • Generate DEP- Criteria checklists: all TEST- pass in staging, performance baselines met, security review complete
  • Define DEP- Rollback entries such as automatic rollback when 5xx error rate >2% for 5 minutes
  • Produce DEP- Validation entries: post-deploy smoke tests, key-journey verification, metric baseline confirmation
  • Export DEP- items to feed runbooks, monitoring alerts, and go/no-go gates for GTM

FAQ

You receive DEP-XXX entries for Environment, Criteria, Rollback, and Validation with fields for stage, owners, verification, thresholds, and linked IDs.

How strict should release criteria be?

Make functional, performance, and security criteria must-haves; keep operational and documentation items as should-haves but with clear owners and timelines.

Which rollback pattern should I pick?

Choose based on risk and cost: canary for early detection, blue-green for instant rollback, rolling for low complexity, feature flags to decouple release from deploy.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational