Specroot Waitlist open

Templates

Free to copy, no sign-up. Each template comes with a worked example, and with what to do when the requirements change after it is signed.

Sign-off

Getting the requirements, each change to them, the result, and finally the project, accepted in writing on a named version.

  • Change control board (CCB): members, charter and process

    What a change control board is, who sits on it, what it decides, a CCB charter template with an example, how a meeting runs, and CCB vs CAB vs product owner.

  • Change log template for project requirements

    A change log template for project requirements: what to record, an example, change log vs change request log, and how to keep one in Excel, Confluence or Jira.

  • Change request template for software projects

    A free change request template for software projects, with a filled-in example, a change request log, and the email that asks the client for a decision.

  • Requirements sign-off template

    A free requirements sign-off template and email to copy: what to include, how to get a client to actually sign off, and what to do at the first change.

  • Change impact analysis

    A change impact analysis template and a worked example for software: requirements, code, data, tests, cost and dates a change touches, and how to find them.

  • Decision log template

    A decision log template to copy, a worked example, what to record, how to keep it, and decision log vs ADR, RAID log and change log — plus Excel and Confluence.

  • Project scope statement template

    A project scope statement template for software projects, a filled-in example, in scope vs out of scope, and scope statement vs project charter, SOW and WBS.

  • Project sign-off template

    A free project sign-off template and email, with an example, phase sign-off, a closure checklist, and what to do when the client won't sign off.

  • Test case template and examples

    A free test case template to copy into a spreadsheet, with examples for a payment and a login page, positive and negative cases, and how to write test cases.

  • UAT test plan template

    A free UAT test plan template with test case and script examples, entry and exit criteria, a UAT checklist, and who does UAT — plus UAT vs SIT and QA.

  • UAT sign-off template

    A free UAT sign-off template and email to copy: what the document includes, the sign-off criteria, and how to tie acceptance to the version that was approved.

Requirements documents

The documents a software project is agreed and built from.

Gathering and writing requirements

From the first questions to one requirement at a time: user stories, use cases, acceptance criteria, non-functional requirements, the definition of done, and specs for AI coding agents.

  • Spec-driven development example

    A complete spec-driven development example: one feature's spec, plan, tasks and tests, then a change request, version 2 and what it touches, in three formats.

  • Acceptance criteria template: Given/When/Then examples

    Free acceptance criteria templates (Given/When/Then and checklist), with examples for user stories and APIs, and how they differ from the definition of done.

  • Business rules vs requirements, with examples

    Business rules vs requirements, with examples: rule types, and how a business rule differs from functional requirements, business logic and acceptance criteria.

  • Types of requirements, with examples

    Types of requirements in software engineering with one example each: business, user, functional, non-functional, rules, constraints. Plus requirements vs specs.

  • User story template and examples

    A free user story template with acceptance criteria, software examples, a Jira version, INVEST, splitting, and user story vs use case, epic and task.

  • EARS requirements: syntax and examples

    EARS requirements syntax: the five patterns with examples, a template to copy, how to rewrite a requirement in EARS, EARS vs Gherkin, and EARS in Kiro.

  • Gherkin examples

    Gherkin examples to copy: the keywords, a full feature file, Scenario Outline with Examples, data tables, Background, Rule, a template and best practices.

  • MoSCoW prioritization

    MoSCoW prioritization explained: must, should, could and won't have, with a worked example, a template, the 60% rule, and MoSCoW vs RICE, Kano and WSJF.

  • Requirements review checklist

    A requirements review checklist to copy, the characteristics of good requirements (IEEE 830, ISO 29148), a worked review, words to flag, and how to run it.

  • Definition of done: examples and a checklist

    What a definition of done is, examples for software teams, a checklist to copy, and the definition of done vs acceptance criteria vs definition of ready.

  • Non-functional requirement examples

    Non-functional requirements examples by type: performance, security, availability, usability, with a checklist, a template and how to make them testable.

  • Requirements gathering questions to ask

    Requirements gathering questions to ask clients and stakeholders, by topic, with a first-meeting list, an interview template and how to run the interview.

  • Use case template and example

    A free use case template with a filled-in example: actors, preconditions, main success scenario, alternative and exception flows, and use case vs user story.

  • Spec template for spec-driven development (spec.md)

    A free spec.md template for spec-driven development with Claude Code, Cursor or Copilot: what goes in a spec, an example, and spec.md vs CLAUDE.md.

What Specroot is