Simple workflow for consistent, quality development
- Read last entry in
docs/project-state/change-log.md - Verify previous claims by running tests:
./gradlew test - If previous work is broken/incomplete, fix it FIRST
- Read
docs/project-state/current-status.md - Run
./gradlew cleanto verify build health - Check
docs/project-state/priorities.mdfor current goals
- TIER 1 errors exist? Fix build/test failures FIRST
- No TIER 1 errors? Pick smallest TIER 2 improvement
- Research needed? Use Brave Search/Context7 MCP before coding
- Change ONE thing at a time
- Test immediately:
./gradlew buildor./gradlew test - If it breaks, rollback before continuing
- Use
docs/templates/simple-change-log.mdfor important changes - Use
docs/templates/mcp-research-notes.mdif MCP research helped
git add .
git commit -m "Agent Session [DATE]: [what you fixed/improved]"
git push origin HEAD- Update
docs/project-state/current-status.mdif project state changed - Update
docs/project-state/priorities.mdwith next steps
- Never use GitHub MCP for commits (causes sync conflicts)
- Fix TIER 1 errors before anything else (build/test failures)
- Make small changes only (one file, one issue)
- Test immediately after each change
- Research complex issues before guessing
This checklist focuses on the essential quality gates while eliminating bureaucratic overhead.