<aside> 🚀

Purpose: Turn a vague automation or bug-fix request into a bounded, testable, safely delivered project.

</aside>

Public QA preview

The completed CSV sample records expected and actual results for four checks. Each row is marked PASS because the outcomes match. If the fixture or actual result is missing, keep the check NOT PROVEN until it is verified.

CSV sample test evidence: four expected-versus-actual checks marked PASS

CSV sample test evidence: four expected-versus-actual checks marked PASS

Five-minute setup

  1. Read the seven gates below.
  2. Open the sample project in Projects.
  3. Duplicate the sample for your next client request.
  4. Complete Intake and Scope before implementation.
  5. Use the matching prompt from Prompt Library.
  6. Record implementation work and evidence in Work Items.
  7. Deliver only after the QA gate has evidence.

Workflow map

Gate Owner role Required input Required output Exit condition
1. Intake Intake Strategist Raw request and available evidence Complete client brief Goal, environment, constraints, and evidence captured
2. Scope Scope Manager Completed intake brief Accepted scope One deliverable, exclusions, and definition of done are explicit
3. Plan Solution Architect Approved scope and reproduction findings Implementation and rollback plan Dependencies, risks, tests, and approvals are documented
4. Build Builder Approved plan and READY build gate Working change Changed artifacts and deviations are recorded
5. Test QA Engineer Definition of done and change record Verification evidence Expected, actual, edge, regression, and rollback checks are complete
6. Deliver Delivery Manager Passed QA evidence Client handoff Usage, limitations, evidence, rollback, and revision terms are ready
7. Evaluate Evaluator Project record, evidence, and feedback Score and reusable learning Quality is scored and sensitive information is removed from reusable assets

Operating rules