Flutter Documentation

Generate and maintain project documentation that helps the team understand, extend, and onboard onto the Flutter app.

Workflow

1. Identify what needs documenting — new feature, architecture decision, release, or onboarding gap.
2. Read the project state first — inspect README.md, docs/, lib/, pubspec.yaml. Never write docs that contradict the actual code.
3. Choose the right template from templates/ (see Output Artifacts below).
4. Draft the document — fill all required sections; mark [TODO] for sections requiring user input.
5. Review for accuracy — every file path, command, and class name must exist in the current codebase.
6. Update the README if new commands, env vars, setup steps, or architecture patterns were introduced.
7. Cross-link — new feature docs should be referenced from docs/architecture/technical_plan.md or the relevant ADR.

Documentation Rules