Templates

Templates: how to use them

Copy-ready templates for the Developer path and the Master Developer rank.

Each template is plain Markdown. Copy it into a file in your own repository. Fill it in with your own words.

Template Used in
Product brief Week 1
Personas and demographics Week 2
Touch points and journeys Week 2
Repository map Week 1
Integrations register Week 1
Epic roadmap Week 3
Weekly note Every week
Decision record Master Developer
Catalogue entry Week 6 and Master Developer
Change record Master Developer

Rules

  1. You write the content. AI may format and check what you decided. See People write epics.
  2. Mark every guess. Use K for known and G for guess.
  3. No secrets, no real customer data. Use fake data in examples.
  4. Keep the file in git. It is the source of truth.
  5. Say how you used AI. See Disclose AI use.

The examples use TrailMug, a fictional reusable-cup subscription.

Back to the library