# Requirement Document: DevQA Workflow Test Run

Created: 2026-06-06T09:39:32+00:00
Run ID: DEVQA-TEST-2026-06-06
Current stage: Requirement Doc Created

## Scope Summary

Test-run the saved DevQA workflow as a reusable Hermes multi-agent/profile process. The workflow should accept a client requirement, route it through separate BA, QA, Designer/Stitch, Dev, and QA-Dev Loop agent/profile stages, and track status in a Google Sheet.

## In Scope

- Detect prior workflow status before starting a run.
- If no existing requirement document is found, create one.
- Create a Google Sheet tracker for workflow status and references.
- Build a BA matrix with screens/modules/integrations/business rules/roles/access.
- Create QA test cases linked to BA matrix requirements.
- Run QA coverage review against BA matrix and requirement doc.
- Create design prompts for Stitch/design generation.
- Stop at BA Approval Gate if actual client project details are missing.

## Out of Scope for This Test Run

- Building production application code.
- Running real QA against a deployed app.
- Creating final Stitch design artifacts beyond design prompts.
- Client signoff, because this is a workflow smoke test.

## Agent/Profile Ownership

- Client Intake Agent/Profile: captures raw requirement and attachments.
- BA Orchestrator Agent/Profile: creates requirement doc, BA matrix, BA approval gate.
- QA Test Case Agent/Profile: creates test cases and tracks QA status.
- QA Coverage Reviewer Agent/Profile: checks requirement/test coverage completeness.
- Designer/Stitch Agent/Profile: creates Stitch-ready design prompts.
- Dev Agent/Profile: implements approved requirements only.
- QA-Dev Loop Coordinator Agent/Profile: manages fail/fix/retest cycle and final status.

## Users / Roles

- Client / Product Owner
- BA Orchestrator
- QA Agent
- QA Coverage Reviewer
- Designer / Stitch PM
- Dev Agent
- QA-Dev Loop Coordinator

## Screens / Modules

- Client Requirement Intake
- Requirement Document
- BA Matrix
- QA Test Cases
- QA Coverage Review
- Design Prompts
- BA Approval Gate
- Dev Implementation Tracker
- QA-Dev Loop Tracker
- Final Outcome Report

## Integrations

- Hermes profiles: businessanalyst, qaagent, stitchpm, coder
- Google Sheets for workflow tracking
- Google service account for sheet creation
- Stitch MCP/design workflow when design generation is requested

## Business Rules

1. A workflow run starts by checking the last known status.
2. If no previous status exists, start as a new run.
3. If a requirement document exists, reuse it; otherwise create one.
4. BA matrix and QA test cases must cross-reference each other.
5. QA coverage review must happen before BA Approval Gate.
6. Dev Agent cannot start until BA Approval Gate is approved.
7. QA-Dev Loop continues until every test case is Passed, Blocked, or Clarification Required.
8. Final run status must be one of Passed, Blocked, or Clarification Required.

## Acceptance Criteria

- AC1: Prior status is checked before starting the run.
- AC2: Requirement document exists for the run.
- AC3: Google tracking sheet is created and reference link is available.
- AC4: BA matrix exists with screens, modules, integrations, business rules, roles, and access.
- AC5: QA test cases exist and link to BA requirement IDs.
- AC6: QA coverage review identifies missing or covered requirements.
- AC7: Design prompts exist for the main workflow screens.
- AC8: BA Approval Gate returns Passed, Blocked, or Clarification Required.

## Clarifications Required

- Actual client project/product requirement is not supplied yet, so this smoke test cannot proceed to real Dev implementation.
- If the next run targets a real project, provide the client requirement or existing requirement document first.