pw-deliberate

To create a checkpoint-driven implementation plan, provide a problem statement or research.md content to generate a plan.md containing 3-4 checkpoints with goals, files, success criteria, and verification commands. It synthesizes PO and TL perspectives to structure the plan.

Aligning product and technical perspectives requires a deliberation synthesis that evaluates user value and acceptance criteria from a PO view, alongside architecture and dependencies from a TL view, resolving tradeoffs into a cohesive checkpoint plan.

Yes, you can use a GitHub issue number as input to generate a structured feature plan. The process evaluates the issue to produce a plan.md featuring 3-4 checkpoints, each with specific goals, tasks, files to modify, and verification commands.

Feature planning supports team collaboration by identifying parallelization opportunities during the technical assessment. The generated checkpoint plan includes parallelization notes for each stage, allowing team members to work on tasks concurrently.

Before generating a checkpoint plan, you need inputs such as a research.md file, problem statements, or GitHub issue numbers. These inputs are evaluated from PO and TL perspectives to produce the structured implementation plan.

Multi-persona deliberation improves implementation plans by combining PO scope evaluation with TL architecture assessment. This synthesis produces a plan with clear tradeoffs, resolution notes, and feature-flag sections, ensuring technical implementation aligns with product value.