# Per-post documentation (`NEXT_STEPS`, `COMPLETION_*`)

**Last Updated:** 2026-04-01

## Purpose

Some posts under `docs/content/blog/posts/{category}/{slug}/` include **`NEXT_STEPS.md`**, **`COMPLETION_SUMMARY.md`**, or **`COMPLETION_REPORT.md`**. These are **optional, post-specific** logs from improvement sprints.

## Current guidance

| File | Use |
|------|-----|
| **`IMPROVEMENT_PLAN.md`** (when present) | Preferred SSOT for **active** structured improvements (phases, checklists). |
| **`NEXT_STEPS.md`** | Optional narrative / manual QA reminders. **Do not** recreate blog-wide topics here—use [`../NEXT_STEPS.md`](../NEXT_STEPS.md). |
| **`COMPLETION_*.md`** | Historical snapshot when a sprint finished. **No requirement** to add new ones; prefer updating `IMPROVEMENT_PLAN.md` and Git history. |

## Cleanup

- Do **not** bulk-delete `NEXT_STEPS.md` files without human review: many contain live manual QA checklists.
- Completed `COMPLETION_*` files may be moved to `docs/archive/` in a dated folder if you need to reduce clutter; update any internal links.

## Hub

- Blog system backlog: [`../NEXT_STEPS.md`](../NEXT_STEPS.md)
- Index: [`../CONTENT_SYSTEM_INDEX.md`](../CONTENT_SYSTEM_INDEX.md)