flame-harness-retro

To generate a retrospective report for a completed Flutter game build, you can run this skill to evaluate build logs and QA feedback against nine core harness-design principles. It analyzes your pipeline artifacts and produces a formal retrospective report to finalize the project state.

A game development pipeline audit evaluates the integrity and quality of your completed build process against nine core harness-design principles. It analyzes configuration, state, contract, and log files to ensure generator-evaluator separation and compile a formal verification report.

Yes, running a quality assurance audit on a Flame game requires access to the full suite of harness artifacts. You must provide configuration, state, contract, and log files so the evaluator can analyze build logs and contract adherence effectively.

Yes, you can get actionable improvement items after finishing a Flutter game pipeline. The evaluation generates specific Keep, Improve, and Try items based on the QA feedback and contract criteria verification to refine future development cycles.

The best way to verify contract adherence in a Flutter game development pipeline is to audit the completed build logs and harness artifacts against core design principles. This process checks contract criteria and visual evidence to produce a formal status report.

Your Flutter game build needs a formal retrospective to ensure objective quality assurance and closure in AI-driven development. It provides a structured evaluation of pipeline integrity, confirming contract adherence before the project state transitions to completed.