change-guard

To check change request coverage, analyze the request against existing PRD, architecture, UI spec, and development plan documents. This coverage analysis identifies gaps and conflicts, classifying the change as a clarification, enhancement, or new requirement before implementation begins.

Change impact assessment analyzes requested modifications against project documentation to determine coverage gaps and required downstream updates. It classifies the change type and produces structured routing output, guiding orchestrators whether to proceed, amend documentation, or cascade changes upstream.

Classify a change request by comparing it against current PRD, ARCH, UI-SPEC, and DEV-PLAN documents. The classification depends on document coverage and conflicts, labeling the request as a clarification, an enhancement, or an entirely new requirement.

You need to update project documentation before proceeding when change analysis reveals coverage gaps or conflicts with existing specs. The impact routing output will indicate whether to amend the PRD or architecture documents first to prevent ambiguity during implementation.

Yes, document traceability analysis produces a structured routing output designed for orchestrator decision-making. It determines whether to proceed with the change, amend documentation first, or cascade required updates upstream based on detected conflicts.

The best way to analyze a new workflow step is to check it against current PRD and UI specifications. This impact assessment determines whether the step fits existing documentation or requires a full PRD rewrite and downstream architecture updates.