proceed

What problem does it solve?

End-to-end ADLC pipeline orchestration from a drafted requirement through validation, architecture, implementation, verification, and merge, reducing manual handoffs and ensuring auditable progress.

Core Features & Use Cases

• End-to-end pipeline execution: validate → architect → implement → reflect + review → create PR → wrapup, with optional canary deployment.
• Gate-based execution with state persistence: maintains a pipeline-state.json to track current phase, completed phases, and per-task progress to enable resume after interruptions.
• Parallel and subagent execution: dispatches agent-based work where appropriate and supports a subagent mode for sequential in-context runs.
• Preflight, safety, and traceability: environments are prepared with worktrees, shared context is loaded once, and phase transitions are strictly enforced.
• Use case: a team runs a single command to drive a drafted REQ from spec to deployment, with full traceability and rollback paths.

Quick Start

Run /proceed REQ-xxx to drive a requirement from spec through deployment.