ship-phase

To execute a plan phase end-to-end, invoke the process with a plan file and phase number. It automatically sequences implementation, lint/tests, optional builds, and a final 7-category audit to validate deliverables and generate status reporting.

A stage-based workflow for shipping phases enforces sequenced execution across IMPLEMENT, QUALITY GATE, BUILD CHECK, and AUDIT stages. This controlled rollout mechanism ensures phase deliverables are validated automatically, reducing manual coordination and drift.

No, you cannot run multiple phases in a single invocation. The process is plan-scoped for safety, executing and validating exactly one phase per run to ensure controlled rollouts and easy rollback for each phase.

You need to provide a plan file and a phase number as inputs to trigger implementation. The process uses these inputs to coordinate the end-to-end execution, running lint/tests, optional builds, and a final 7-category audit to close the loop.

The best way to validate deliverables is using an automated end-to-end phase execution process. It implements the phase, enforces quality gates, runs builds, performs a 7-category audit, and automatically generates a ship status report with audit results.

Phase execution fails before the audit stage if preceding quality gates or build checks are not passed. The workflow enforces strict sequencing across IMPLEMENT, QUALITY GATE, and BUILD CHECK stages, ensuring only validated phases reach the final 7-category audit.