skills.rest
AlexHorovitz
AlexHorovitzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

SSD Methodology

Enforce machine-checkable gates, ADR adherence, and frontmatter validation for deployable software.

Updated Mar 25, 2026
Search Tags:#methodology#feature-flags#production-parity#continuous-deployment#ssd#gate-rules
One-click install
npx skills add https://github.com/AlexHorovitz/skills --skill ssd-methodology
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SSD Methodology
Source: https://github.com/AlexHorovitz/skills/tree/main/methodology
Command: npx skills add https://github.com/AlexHorovitz/skills --skill ssd-methodology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

SSD Methodology provides a principled framework to keep software in a deployable, production-ready state throughout development, reducing late-stage integration risk and surprise fixes.

Core Features & Use Cases

  • Constant production parity from day one, so deployments never become last-minute bottlenecks.
  • The shippable-state invariant: every commit can be deployed and passes tests, with no broken user-facing features.
  • Feature flags over long-lived branches enable incremental delivery across web, mobile, and headless stacks.
  • Automated governance through gate rules and a machine-checkable policy surface for auditable compliance.

Quick Start

Integrate a gate-driven CI/CD discipline and begin shipping small, testable changes to production with feature flags.

Frequently Asked Questions about SSD Methodology

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

FAQPage Schema
How do I keep software deployable at all times during development?▼

To keep software deployable at all times, enforce the shippable-state invariant so every commit passes tests and deploys without breaking user-facing features, maintaining constant production parity from day one.

Why use feature flags instead of long-lived branches for continuous deployment?▼

Feature flags enable incremental delivery across web, mobile, and headless stacks by decoupling deployment from release, avoiding the integration risks and bottlenecks created by long-lived branches.

How do I automate governance and compliance for continuous deployment?▼

Automate governance by applying machine-checkable gate rules, ADR adherence, and frontmatter validation to create an auditable policy surface that enforces compliance throughout the development lifecycle.

Can I apply the shippable-state invariant to mobile and headless stacks?▼

Yes, the shippable-state invariant applies to web, mobile, and headless stacks, ensuring every commit is production-ready and deployable across diverse environments seeking frequent, risk-conscious delivery.

What is a gate-driven CI/CD discipline and how does it reduce deployment risk?▼

A gate-driven CI/CD discipline uses machine-checkable rules to validate commits before deployment, enforcing production parity and test compliance to reduce late-stage integration risk and surprise fixes.

When should I not use feature flags for incremental delivery?▼

Avoid using feature flags when your project lacks production parity or automated gate rule enforcement, as untested flag combinations can introduce unexpected behaviors and complicate auditable compliance.

Related Skills

Explore More Software Engineering Skills→
ksciuskscius
2

devops-skills

Pre-validate Terraform, Docker Compose, Kubernetes manifests, and CI pipelines.

Community
Intermediate
aws-samplesaws-samples
18

quality-gates

Validate AIDLC phase gates for compliance and operational readiness.

Official
Advanced
harnessharness
80

enforce-slsa

Add an SLSA Verification step to Harness pipelines for provenance attestations.

Official
Advanced
charchesscharchess
1

vixens-gitops

Manage Vixens GitOps pull requests, production promotion, and branch protection.

Community
Advanced