workflow-feedback

To capture workflow feedback, use the Capture mode to standardize observations from builds or autopilot runs in downstream projects. It reads sources like .dev-workflow/feedback.md and lessons-learned, outputting structured docs to route upstream.

Routing lessons learned upstream is handled by the Review mode in the AEP repository, which reviews captured observations and routes upstream candidates to documentation to improve learning loops and process improvements.

You need to standardize workflow observations after builds or autopilot runs in downstream projects to ensure feedback is structured and ready for upstream routing to AEP documentation.

Yes, workflow feedback routing works without external dependencies. It operates internally by reading sources like .dev-workflow/feedback.md and lessons-learned, then outputting structured docs to docs/ and guidance for downstream synchronization.

Yes, you can improve downstream-aware learning loops by capturing and standardizing observations from builds and reviews, then routing them upstream to the AEP repository for documentation and process improvements.

Manual capture lacks standardization, making upstream routing inefficient. This approach standardizes observations from downstream projects into structured docs, ensuring consistent guidance for downstream synchronization and learning loops.