product-implement

To generate a PRD from Product Decision Records, run the implement workflow to orchestrate a multi-agent DAG that organizes PDRs by feature-area and outputs a unified PRD.md file. The workflow executes in topological order to resolve cross-area conflicts.

Maintaining traceability between PDRs and a final PRD requires enforcing source links during generation. This Skill orchestrates PDRs into a comprehensive document while enforcing traceability to original PDR sources throughout the multi-agent workflow.

Yes, you can resume PRD generation because the workflow uses state persistence for resumability. This state persistence supports collaboration across agents and allows the DAG orchestration to recover and continue the phase-based execution.

A DAG workflow helps organize product requirements documentation by generating per-section content in topological order. This phase-based planning and execution resolves cross-area conflicts across multiple PDRs to produce a cohesive PRD output.

Yes, this PRD generation tool supports canonical lifecycle management of accepted PDRs. The workflow integrates this lifecycle management with phase-based planning and execution to ensure PDRs remain organized and persistent.

To resolve cross-area conflicts when consolidating product decisions into one document, the workflow orchestrates PDRs by feature-area and generates content in topological order. This structured DAG execution ensures conflicting decisions are resolved into a unified PRD.