.claude/skills/workflow/workflow-state/SKILL.md
How to transition workflow state between review stages. Rules for setting review_stage and review_result fields on Stories and Epics.
npx skillsauth add brdohman/agile-maestro workflow-stateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Set review_stage and review_result directly in the same TaskUpdate call. No helper function needed. Always include a structured comment in the same call.
Submit for code review: review_stage: "code-review", review_result: "awaiting"
Pass code review: review_stage: "qa", review_result: "awaiting"
Fail code review: review_stage: "code-review", review_result: "rejected"
Pass QA: review_stage: "product-review", review_result: "awaiting"
Fail QA: review_stage: "qa", review_result: "rejected"
Pass product review: review_stage: null, review_result: null (+ status: "completed")
Fail product review: review_stage: "product-review", review_result: "rejected"
Fix and resubmit: review_stage: "code-review", review_result: "awaiting"
Any rejection restarts at code-review. After fixing, always set review_stage: "code-review", regardless of which stage rejected.
Both fields must be set together. review_stage and review_result are always paired. Never set one without the other.
Tasks never get review fields. Only Stories and Epics go through the review cycle. Tasks complete directly.
Read before write. Always call TaskGet before TaskUpdate to preserve the existing comments array.
Every transition requires a comment. Include a structured comment in the same TaskUpdate call.
VALID: review_stage: "qa", review_result: "awaiting"
VALID: review_stage: null, review_result: null
INVALID: review_stage: "qa", review_result: null (unpaired)
INVALID: review_stage: null, review_result: "awaiting" (unpaired)
.claude/docs/WORKFLOW-STATE.mdreview-cycle.claude/rules/global/task-state-updates.mdtesting
XCTest patterns for macOS Swift apps. Unit tests, async tests, Core Data tests, mock patterns, and assertion reference. Use when writing or reviewing tests.
documentation
Comment structure and rules for task workflow updates. Use when adding any comment to a task during implementation, review, or fix cycles.
testing
Validate task/story/epic/bug/techdebt metadata against schema v2.0. Run after TaskCreate or TaskUpdate to verify compliance. Returns pass/fail with actionable details.
data-ai
Canonical v2.0 metadata schema field reference for epics, stories, and tasks. Use when creating or validating task metadata.