agile-delivery-workflow

Delivers a focused MVP commit with scoped validation and a clear checkpoint report.

Updated May 18, 2026
One-click install
npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill agile-delivery-workflow-joey-tools
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agile-delivery-workflow
Source: https://github.com/Joey-Tools/codex-private-workflows/tree/main/personal_codex/skills/agile-delivery-workflow
Command: npx skills add https://github.com/Joey-Tools/codex-private-workflows --skill agile-delivery-workflow-joey-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you explicitly ask for an MVP or early usable slice, full delivery gates (broad review, CI waiting, PR readiness) slow down feedback. This Skill produces the smallest useful local commit quickly, then stops at a clear checkpoint instead of silently continuing into the full delivery pipeline. ## Core Features & Use Cases - First-Slice Scoping: Defines the core user-visible behavior, cuts polish and refactors, and stops early with evidence if a dependency blocks the slice. - Focused Validation: Runs the narrowest checks that prove the slice builds or runs, and explicitly reports any skipped broader validation. - Checkpoint Commit & Report: Creates a local commit using repo conventions, then reports the commit SHA, what is usable now, checks run, known gaps, and the recommended next iteration. - Use Case: You ask for an MVP of a new CLI command. The Skill implements just that command, runs a smoke test, commits locally, and hands you a checkpoint summary without opening a PR or waiting on CI. ## Quick Start Ask the agent to build an MVP or early usable slice of the feature you want and stop at a local checkpoint commit.

Frequently Asked Questions about agile-delivery-workflow

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

FAQPage Schema
How do I get an MVP commit without the full delivery process?

Explicitly ask for an MVP, early usable product, or quick iteration. The Skill scopes the smallest useful slice, implements it, runs focused checks, and creates a local checkpoint commit without pushing, opening a PR, or waiting on CI.

When should I use agile delivery instead of a full delivery workflow?

Use it only when you explicitly want an early usable slice for fast feedback, such as MVP or scout work. Ordinary non-trivial tasks should use the standard change delivery workflow with its complete local gate.

Does the MVP checkpoint commit get pushed or turned into a PR?

No. The checkpoint is a local commit only and is not merge-ready by default. Pushing, opening a PR, waiting for CI, or running external review happens only when you explicitly ask to continue to that phase.

What validation runs on an MVP slice?

Only the narrowest checks that prove the slice builds, runs, or can be inspected, such as focused tests, smoke commands, or static checks. Any skipped broader validation is reported explicitly, and full validation is never claimed.

What happens if a dependency blocks the MVP slice?

The Skill stops early, reports the blocker evidence, and identifies the smallest next slice that can proceed. It does not work around the blocker by expanding scope or guessing at a brittle implementation.