Remove docs/topics and docs/specs across melodic-software repos

[kyle-sexton]

Problem

Plans, briefs and design notes live under docs/topics/<name>/ while work is in flight and graduate to docs/specs/<name>/ before merge (docs/conventions/topic-docs/README.md, enforced by scripts/check-contract-slice-prune.sh). The owner wants both trees gone long term, in every repo, and does not want that removal codified inside the plugins themselves.

Current footprint (local clones, 2026-09-30)

• docs/specs/: claude-code-plugins
• docs/topics/: ci-runner, ci-workflows, claude-code-account-rotation, claude-code-proxy, github-iac, medley, provisioning, standards

In claude-code-plugins the convention is referenced by docs/conventions/topic-docs/ (README, schema, examples, CHANGELOG), scripts/check-contract-slice-prune.sh and its baseline and test, scripts/check-docs-naming.sh, scripts/check-docs-only.test.sh, scripts/docs-only-paths.txt, scripts/affected-tests-no-suite.txt, and the commit-convention and config-cascade convention docs.

Scope

1. Decide where durable plan and spec content lives instead (for example the PR body, the issue, or code-adjacent docs), and what happens to the existing docs/specs/ files.
2. Remove the docs/topics/ and docs/specs/ trees repo by repo, with the gates and conventions that require them.
3. Keep the removal out of plugin skill bodies: the plugins should not encode a rule about these paths.

Acceptance

• No docs/topics/ or docs/specs/ directory in any melodic-software repo.
• No CI gate or convention doc still requires either path.

No related PR yet.

🤖 Generated with Claude Code

[kyle-sexton]

Owner decision (2026-10-01): approved the recommendation ("go with recommended", the owner's reply to the batch decision page that listed this question and its recommendation).

Question: where does durable plan and spec content live from now on, and what happens to the 40 files in docs/specs/?

Chosen option A: plans and specs live in the PR body and the linked issue. Delete all 40 docs/specs files outright, including the 3 .py scripts in d1-model-already-knows-measurement/. Git history is the archive (a tag on the last commit that has them is optional). Then remove the topic-docs convention and its gates, one draft PR per repo, starting with claude-code-plugins.

Next: an agent opens the draft PR in claude-code-plugins deleting docs/specs/, docs/conventions/topic-docs/, scripts/check-contract-slice-prune.sh (with baseline and test) and the 10 plugins/*/reference/topic-docs.md files, and editing the other referencing scripts and docs without adding any rule about the removed paths. Then one draft PR per sibling repo removes docs/topics/. Labeled agent-ready.