skills.rest
victorp1leon
victorp1leonCOMMUNITY
Explore all skills by this author →
GitHub

feature-delivery-flow

Orchestrates end-to-end project workflows with stage-specific checkpoints and deliverables.

Updated Mar 6, 2026
Search Tags:#guardrails#spec-first#unit-tests#feature-delivery#smoke-integration#operational-checks
One-click install
npx skills add https://github.com/victorp1leon/openclaw-bakery --skill feature-delivery-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-delivery-flow
Source: https://github.com/victorp1leon/openclaw-bakery/tree/main/.codex/skills/feature-delivery-flow
Command: npx skills add https://github.com/victorp1leon/openclaw-bakery --skill feature-delivery-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clears the path for delivering roadmap features by enforcing scope, spec-first design, and gated checks to prevent misaligned or risky implementations.

Core Features & Use Cases

  • Scope and acceptance criteria definition with explicit done criteria.
  • Spec-first design and documentation to align architecture before coding.
  • Design verification and gatekeeping to ensure contracts and schemas compatibility.
  • Incremental implementation with guardrails and focused changes.
  • End-to-end validation including unit tests, smoke/integration summaries, and operational checks.
  • Manual business validation at handoff when required to confirm real-world readiness.

Quick Start

Outline the feature scope and acceptance criteria, then draft a spec-first design before coding.

Frequently Asked Questions about feature-delivery-flow

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

FAQPage Schema
How do I implement a spec-first feature delivery flow with guardrails?▼

A spec-first feature delivery flow requires defining scope and acceptance criteria, drafting design documentation, verifying schemas, and passing unit, smoke-integration, and operational checks before handoff.

What is the best way to enforce acceptance criteria and scope during feature implementation?▼

Enforcing acceptance criteria and scope requires explicit done criteria and gated checks across design, implementation, and validation phases to prevent misaligned or risky implementations.

Does feature delivery with guardrails require design verification before coding?▼

Yes, feature delivery with guardrails requires spec-first design documentation and design verification to align architecture and ensure contracts and schemas compatibility before incremental implementation.

How do I validate smoke-integration summaries and operational checks for feature delivery?▼

Validating smoke-integration summaries and operational checks is part of end-to-end validation, followed by manual business validation at handoff to confirm real-world readiness.

What is the purpose of gated checks in end-to-end feature delivery?▼

Gated checks in end-to-end feature delivery clear the path for delivering roadmap features by verifying scope, design, implementation, and validation to prevent risky implementations.

When do I need manual business validation during feature handoff?▼

Manual business validation during feature handoff is required when specific operational checks are passed, ensuring the feature meets real-world readiness criteria before final release.

Related Skills

Explore More Software Engineering Skills→
lionbenjaminlionbenjamin
15

specify

Draft product specifications with problem, goals, user stories, and acceptance criteria.

Community
Intermediate
jkrummjkrumm

audit

Audit VPS system resources, containers, network connectivity, and backups.

Community
Advanced
josuenavarroaguadojosuenavarroaguado

ci-cd-and-automation

Automate GitHub Actions CI/CD pipelines with quality gates and preview deployments.

Community
Advanced
mikivujkovicmikivujkovic
1

feature-flow

Guide feature delivery through DDD, BDD, TDD, and Git phases.

Community
Basic