plan-review

To analyze downstream prompt impact after a milestone, run a plan-review to evaluate architecture changes and record how they affect downstream prompts, rules, and reports. This process ensures traceable decisions by logging impact data in plan-state artifacts.

Architecture changes break downstream prompts and rules when outdated assumptions persist. A plan-review detects these outdated assumptions, suggests concrete prompt patches without overwriting user prompts, and generates an auditable change log for downstream components.

You can create an auditable change log for downstream prompts by running a plan-review after milestone completion. It records ADDED, CHANGED, REASON, and IMPACT entries for downstream components, ensuring decisions remain traceable across the lifecycle.

Yes, you can review milestone changes without overwriting existing user prompts. The plan-review process detects outdated downstream assumptions and suggests concrete prompt patches, preserving your original prompts while identifying necessary updates.

You need to run a plan-review for your workflow immediately after milestone completion. It bridges planning, prompting, and lifecycle logging by reading architecture baselines, parsing output language and timezone, and updating the plan context.

The best way to maintain an audit trail for architecture changes is to apply plan-review after each milestone. It records impact data in plan-state artifacts, ensuring traceable and auditable decisions for downstream prompts and reports.