Skip to content

Numbered Requirements

  • Before implementing, restate the work as a numbered list of requirements and get it confirmed
  • Write the list to a file in the repository so it can be re-read later, rather than leaving it in chat
  • Cite the requirement number when implementing, when committing and when reporting progress
  • Implement one requirement at a time, and mark it done only when it is verified
  • When the human says “requirement 4 is wrong”, change only what requirement 4 covers
  • Add newly discovered work as a new numbered item instead of widening an existing one
  • Keep a non goals section, and move anything dropped into it rather than deleting it