flowCreate.solutions

Tracker Playbook (Project Standard)

This playbook defines how to structure and use tracking documents (“trackers”) inside a project repository so that multi-step work stays coordinated across contributors and sessions.

Purpose

Trackers are a lightweight “source of truth” for:

  • progress and next steps
  • rules/constraints for contributors (especially AI agents)
  • decisions, blockers, and follow-ups

Required project structure

Every project must keep trackers in:

trackers/
├── readme.md                 # short entrypoint
├── tracker_creation_guide.md # how to create trackers + template skeleton
└── files/                    # tracker files live here
    ├── <topic>_tracking.md
    └── ...

Required files

  • trackers/readme.md
    • Must explain what trackers are and point to trackers/tracker_creation_guide.md.
  • trackers/tracker_creation_guide.md
    • Must include required sections + template skeleton.
  • trackers/files/
    • Must contain all tracker documents.

For copy/paste templates:

  • Use backend/06_trackers/project_trackers_readme_template.md for the project readme.
  • Use backend/06_trackers/tracker_creation_guide.md as the project creation guide.
  • Use backend/06_trackers/examples/example_tracker.md as a worked example.

When to create a tracker

Create a tracker when work:

  • touches multiple modules/files
  • spans multiple sessions/prompts
  • requires verification/auditing/standardization
  • has meaningful constraints (security, migrations, scope boundaries)
  • is explicitly requested by the lead

Naming convention

  • Store trackers as trackers/files/<topic>_tracking.md.
  • Keep names stable and descriptive.

Maintenance rules

  • Update the tracker at the start and end of each work session.
  • Treat the tracker as the source of truth over personal memory.
  • Record failures and rollbacks as well as successes.

Standards: what a tracker must contain

Trackers must include:

  • Header: started date, owner, objective
  • Ground rules: explicit agent instructions and safety constraints
  • Workflow: repeatable checklist (read → verify → propose → implement → validate)
  • Progress: ✅/🔄/⏳/🚫 structure (checkbox list or table)
  • Notes & follow-ups: blockers, decisions, next steps