Appendix C. Checklists and Templates

This appendix can be used as a quick reference while working on a project.

Checklist Before Creating a Specification

• the purpose of the feature is clear;
• the audience is known;
• there are scope boundaries;
• there is a list of what is out of scope;
• stack constraints are known;
• there is at least one verifiable result;
• it is clear which roadmap phase is being implemented;
• no secret or access is required that is not available in the local environment.

Checklist Before Implementation

• requirements.md is created;
• plan.md is created;
• validation.md is created;
• the specification is committed;
• the agent was given links to files, not a long chat history;
• the current branch is clean or understood;
• feature boundaries do not conflict with tech-stack.md;
• there are no unrelated refactorings in the plan.

Checklist Before Merge Request

• all modified files are related to the feature;
• mandatory facts from validation.md are verified;
• failed facts are explicitly listed;
• deferred facts have a reason;
• new hooks and MCP servers were reviewed;
• secrets did not leak into specifications, logs, or memory;
• CHANGELOG.md is updated if the project maintains one;
• the roadmap is updated or there is a reason not to update it in this branch.

Merge Request Template

## Specification

- Folder: `specs/YYYY-MM-DD-feature-name/`
- Roadmap phase:

## What Changed

- 

## Verification Facts

- [ ] `npm run typecheck`
- [ ] `npm test`
- [ ] 

## Unverified or Deferred Facts

- 

## Changes Outside Feature Boundaries

- None / list:

## What the Reviewer Should Check Especially Carefully

- 

Retrospective Template

# SDD Retrospective

## What the Specification Described Correctly

## What the Agent Had to Infer on Its Own

## What the Verification Caught

## Which Facts Were Weak

## What to Transfer to QWEN.md or specs/

## What to Remove from the Process

Checklist for a New Session After /clear

• the agent has read QWEN.md or AGENTS.md;
• the agent has read mission.md;
• the agent has read tech-stack.md;
• the agent has read the relevant feature folder;
• the agent knows which files must not be changed;
• the agent knows which verification commands are expected;
• the agent will stop after the report if the task is research-only.

Minimal Prompt for Implementation Review

/clear
Read @QWEN.md, the current feature specification, and git diff.
Compare the implementation with requirements.md, plan.md, and validation.md.
Show:
- matches;
- discrepancies;
- unverified facts;
- changes outside feature boundaries.
Do not modify files.

Minimal Prompt for Replanning

/clear
Read @specs/mission.md, @specs/tech-stack.md, @specs/roadmap.md,
recent feature specifications, and @CHANGELOG.md.
Show what needs to be updated before the next phase.
Do not modify files until I approve.