workflow-work

name	workflow-work
description	Execute plans into production-ready code with task tracking, incremental validation, and progress updates.

Workflow Work

Workflow

1. Read sprint doc in docs/sprints/ and clarify ambiguities before coding.
2. Use the sprint doc task board as the single tracker (no separate todo file by default).
3. If sprint tasks are incomplete, refine them in place before implementation:
   • ensure every MVP requirement and critical flow has at least one sprint task
   • encode dependencies directly in the sprint doc
4. Preserve architecture baseline while implementing:
   • Rails server-rendered responses
   • Phlex reusable components (composable primitives with controlled variants)
   • Stimulus behavior
   • Turbo/Hotwire Native-compatible navigation
   • Tailwind + daisyUI layered through project semantic tokens only
   • custom brand palette/fonts/illustration mapped to semantic tokens
   • no default daisyUI theme shipped unchanged
   • tokenized styling (no ad-hoc visual patches)
5. Implement in small logical increments.
6. Run focused tests/lint after each increment.
7. Capture screenshot evidence for affected web/native shells when UI changes are included.
8. Mark completed sprint tasks in the source sprint doc.
9. Record review follow-ups in the sprint's "Review Findings Queue".
10. Prepare concise summary of completed work, tests run, screenshot checks, and remaining risks.