v0.16 — Template filenames now include the full form

People were getting confused by the bare template acronyms. Template files now carry the acronym and the full form, and the harness refers to each artefact type as `ACRONYM — Full Form` everywhere.

What changed

• All 10 template files renamed to `{ACRONYM}-{Full-Form}.md` (history preserved via `git mv`):
  `BRD-Business-Requirements-Document.md`, `CR-Change-Request.md`, `BR-Bug-Report.md`, `AI-Feature-Spec.md`, `PD-Product-Documentation.md`, `TIP-Technical-Implementation-Plan.md`, `TC-Test-Cases.md`, `DIA-Diagram.md`, `ERD-Entity-Relationship-Diagram.md`, `CLQ-Client-Clarification-Request.md`
• Every `templates/*.md` path reference updated in `CLAUDE.md` and its `.cursor` / GitHub Copilot mirrors, `README.md`, and the website source.
• Rule 0 capabilities table and the Rule 1 confirmation prompt now show acronym + full form.
• Rule 6 documents the naming convention.

Backwards compatible

A bare acronym in a request (e.g. "write the BRD") still classifies normally — the full form is how the agent writes back, not something you must type.

v0.15 — Core skills vs power tools

Core skills and power tools are now formally separated

Core skills are the ten templated artefacts — BRD, PD, TIP, TC, AI, BR, CR, DIA, ERD, CLQ (plus the Retrospective BRD Update). Every one is produced from a template in templates/. Paste a raw request and Baxter handles the rest.

Power tools are six slash-command workflows. Their outputs may have a defined structure, but that structure lives in each command file in .claude/commands/ — never in templates/.

Changes

• New /validate-release command — Release Validation is now a first-class power tool with its own command file. Plain-language triggers ("validate the Sprint 95 release") still work.
• New /generate-samples command file — sample data generation now has a command file like every other power tool.
• Module registry structure moved — templates/MR.md is removed; the canonical structure now lives inside the /generate-module-registry command file.
• All commands are project-agnostic — fixed output structures with generic examples; module names and groupings are read from the connected project's module registry at runtime.
• Website — core skills vs power tools differentiated across every page; fixed a homepage build failure that had been blocking deploys.
• CLAUDE.md — Rule 0 split into two capability tables; Rule 6 enforces the template/command boundary.

Upgrade note

All commit SHAs changed in this release cycle — re-clone rather than pulling into an existing clone.

v0.13 — Flat folder structure

Breaking change: flat folder structure

Both artefacts/ and templates/ are now fully flat — no more issues/ or other/ nesting. Every artefact type has its own dedicated folder, making it obvious at a glance where everything lives.

artefacts/ — one folder per type

Type	New location
Bug Reports	artefacts/bugs/
Change Requests	artefacts/changes/
AI Feature Specs	artefacts/ai-features/
Business Requirements	artefacts/requirements/
Product Documentation	artefacts/product-docs/
Implementation Plans	artefacts/implementation/
Test Cases	artefacts/test-suites/
Diagrams & ERDs	artefacts/diagrams/
Clarifications	artefacts/clarifications/
Module Registry	artefacts/modules/
Sample Data	artefacts/sample-data/

Removed: artefacts/other/ and artefacts/issues/.

templates/ — flat

All 11 templates now live directly in templates/ (BR, CR, AI, BRD, PD, TIP, TC, DIA, ERD, CLQ, MR). Removed: templates/issues/ and templates/other/.

/generate-modules writes to two places

The module registry is now saved to both artefacts/modules/modules.md (versioned artefact) and context/modules.md (working team reference).

Safety: Python files blocked from git

New pre-commit and pre-push hooks block any .py file from being committed or pushed. One-off scripts belong in scripts/ (gitignored).

Documentation

CLAUDE.md, all command files, README, and the entire website (all five pages — homepage, getting-started, templates, philosophy, ecosystem) updated to the new structure. Verified live with zero stale references remaining.

v0.12 — ERD, /generate-modules, and clean context/

What's new

ERD — Entity Relationship Diagram

A new artefact type for visualising database schemas. Baxter reads the codebase schema and generates a Mermaid ERD verified against real table names, column names, and relationships. Saved to artefacts/other/diagrams/.

/generate-modules skill

Run /generate-modules and Baxter scans your codebase — routes, pages, navigation — and drafts a module registry table for your review. Edit any rows, then say save. Writes context/modules.md, which Baxter reads before every artefact to verify module names.

Clean context/ folder

• Glossary removed — the module list is the single source of truth for project-specific terminology
• context/ is now empty by default and fully gitignored — drop in whatever project reference files you need, none of it is ever committed
• Only context/.gitkeep is tracked, so the folder appears after cloning

Website updated

• ERD added to the artefact table and templates page
• /generate-modules documented in the getting-started guide and homepage
• context/ folder added to the folder structure diagram
• Template count updated: Nine → Ten

0.11

Critical Updates and refinements from 0.1 to the Agentic Business Analysis Harness Framework (ABAHF)

0.1

Intial Release