staged-delivery-workflow

What problem does it solve?

This Skill enforces a phased, validated approach to complex implementation tasks that span multiple files or layers, preventing scope creep and unsafe architectural guesses by requiring a clear pre-flight, stage-by-stage progression and using context.md as the single source of truth.

Core Features & Use Cases

• Phase-based workflow (P0–P5): Define and enforce strict stage boundaries (P0 foundations through P3 quality hardening, with optional P4/P5 for hardening and rollout).
• Pre-flight and blocker detection: Mandatory context.md review, declared files-per-stage, and explicit ambiguity surfacing before any code is written.
• Validation gates: Require repository validations at each stage (typecheck, lint, tests) and provide failure protocols and invariant checklists.
• Scope guard and documentation rules: Explicit rules for when to update context.md and how to list residual risks, preventing silent scope expansion.
• Use Cases: Implementing a backend+UI feature that touches multiple packages, coordinating migrations with UI changes, and writing integration tests plus documentation updates.

Quick Start

Use staged-delivery-workflow to break a multi-file feature into P0–P3, declare files per stage, and validate each stage with npm run typecheck && npm run lint && npm run test.