After Hours BuildersTemplates
Back to templates

Week 2

Thin Build Spec

Turn the chosen idea into one user path with acceptance checks and known exclusions.

Use this before a large harness session. The spec should be narrow enough that the harness can implement and verify one visible path.The Build

User path

  • Target user:
  • Starting page or entry point:
  • Action they take:
  • Result they should see:
  • Data that must be saved or shown:

Acceptance checks

  • The page loads on desktop and mobile.
  • The primary action works.
  • Invalid input has a clear error.
  • Disabled providers show disabled states.
  • The route or data write has a focused test.

Do not build yet

  • Extra dashboards.
  • Complex roles.
  • Automations that do not affect the first path.
  • Payment or auth unless the provider setup is verified.