trio:prd-management

To automate the PRD lifecycle, you can use a decision-tree driven orchestration skill that validates preconditions like URS existence and PRD Overview completion before dispatching dedicated agents for module-level planning. This approach ensures URS and PRD alignment, preventing documentation drift and miscommunication across the project.

The best way to structure PRD workflow automation is by using an orchestrator that routes tasks across a defined flow: overview generation, by-module PRD creation, URS-gap checks, and screenshot augmentation. It automatically selects and invokes the appropriate specialized agents with full context, ensuring consistent documentation without writing the PRDs itself.

Precondition validation works by checking if the URS exists and the PRD Overview is completed before allowing any module-level PRD work. If a precondition fails, the orchestration skill guides users to the necessary prerequisite steps, ensuring foundational requirements are met before dispatching agents for detailed module planning.

Yes, you can use automated agent dispatching to handle PRD screenshots and URS gap checks. The orchestration skill evaluates your project state and routes the tasks to dedicated agents, specifically invoking trio:prd-check-urs-gap for alignment validation and trio:prd-add-screenshot for visual augmentation with full context.

Yes, you need a completed PRD Overview before starting by-module PRD documentation. The orchestration skill enforces this precondition to ensure foundational alignment, automatically guiding users to generate the overview first before dispatching agents for module-level PRD creation and subsequent URS-gap checks.

PRD workflow automation fails to dispatch agents for module planning when preconditions like URS existence and PRD Overview completion are not met. The orchestrator validates these requirements beforehand to prevent miscommunication, guiding you to complete the missing foundational steps before routing to the by-module PRD agents.