plan-pipeline-start

To create an implementation plan before coding, this workflow runs five phases: PRD analysis, design review, architecture decisions, dynamic research team, and metrics. It outputs a formal plan document with ADRs to guide development and reduce risk.

An ADR, or Architecture Decision Record, documents design tradeoffs and technical choices. This planning workflow generates ADR artifacts alongside the formal plan file to capture architecture options and prevent scope creep during development.

Analyzing a PRD to surface gaps involves running structured phase outputs against the document. This workflow reviews your PRD and architecture considerations to identify missing requirements and propose technical decisions before execution.

Yes, you can use this workflow to allocate research agents. The scope and team allocation phase determines required research agents and roles, yielding a structured execution plan with clear task assignments.

The best way to document architecture tradeoffs is through a phase-driven planning workflow that proposes architecture options and records ADRs. This captures decisions formally and reduces miscommunication across the team.

Yes, the plan-pipeline workflow auto-transitions to validation when possible. It records phase durations and readiness metrics, then validates the generated plan document through the plan-pipeline workflow.