mattgierhart/prd-driven-context-engineering
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.
18 skills
This skill converts EPICs into production-ready DEP- entries by defining environments, release criteria, rollback triggers, and validation steps.
This skill helps you generate PRD driven context documents to accelerate AI powered product development and documentation workflows.
This skill extracts durable insights from temporary files and updates the Source of Truth during EPIC Phase E, creating SoT entries and an archive manifest.
This skill validates gate criteria before PRD lifecycle advancement, producing pass or block summaries and missing artifact lists.
This skill defines TEST- entries before implementation to ensure clear acceptance criteria across APIs, BRs, and user journeys.
This skill helps surface and prioritize project risks during PRD v0.5 reviews by guiding with questions and actionable mitigations.
This skill creates new Source of Truth SoT files when existing templates don't fit your needs, ensuring proper IDs, frontmatter, and update protocol.
This skill validates and registers new SoT IDs with cross-reference integrity, ensuring format, uniqueness, and correct cross-links across BR, UJ, API, and CFD
This skill defines measurable KPIs for product types, sets targets, and links metrics to go/no-go decisions and downstream processes.
This skill converts vague product ideas into evidence-anchored problem statements with CFD IDs and a structured problem table for PRD v0.1.
This skill classifies a product approach into Clone, Unbundle, Undercut, Slice, Wrapper, or Innovation based on competitive landscape.
This skill converts TECH-, RISK-, and FEA- inputs into ARC- entries and coherent system designs that guide implementation.
This skill helps you create precise RUN- entries with step-by-step operational playbooks for incidents, deployments, and maintenance.
This skill helps define and prioritize features with strategic traceability during PRD v0.3 for market moat, KPIs, and pricing tiers.
This skill helps define launch success metrics, targets, tracking, and dashboards to turn data into actionable launch decisions.
This skill helps you establish and optimize post-launch feedback loops, transforming user input into actionable CFD-, BR-, and RISK- updates.
This skill transforms v0.6 specifications into context-window sized EPICs for v0.7, enabling precise, sharable work packages.
This skill converts user journeys into a structured screen flow, mapping screens, navigation, and design system elements for PRD v0.4.
