Docs-drift sweep at close and land #250

Closed
opened 2026-08-23 20:43:39 +00:00 by john · 0 comments
Owner

/cad-milestone and /cad-land should check the shipped documentation against the code that changed this cycle. A milestone close is where a cycle's accumulated drift is cheapest to catch, and nothing checks it today.

Surfaces a cycle can invalidate

  • README, whose "what it costs to run" section is already stale
  • the plugin manifest
  • CHANGELOG
  • any doc carrying a workflow description, a command list, or an image/diagram

Shape

/cad-land ASKS whether to run the sweep rather than running it unasked. The milestone arm is where it earns its keep.

Scope against the existing command, not over it

/cad-docs-verify already checks claims - paths, commands, symbols, config keys. What it does not do is report omissions well, or cover manifests, changelogs or images. Scope this as the gap around it rather than a second implementation of it.


Moved to GitHub: https://github.com/crenshawdev/cadence/issues/99

This project's tracker is now GitHub; this repository remains the public archive. Closed here as migrated, not as resolved.

`/cad-milestone` and `/cad-land` should check the shipped documentation against the code that changed this cycle. A milestone close is where a cycle's accumulated drift is cheapest to catch, and nothing checks it today. ## Surfaces a cycle can invalidate - README, whose "what it costs to run" section is already stale - the plugin manifest - CHANGELOG - any doc carrying a workflow description, a command list, or an image/diagram ## Shape `/cad-land` ASKS whether to run the sweep rather than running it unasked. The milestone arm is where it earns its keep. ## Scope against the existing command, not over it `/cad-docs-verify` already checks claims - paths, commands, symbols, config keys. What it does not do is report omissions well, or cover manifests, changelogs or images. Scope this as the gap around it rather than a second implementation of it. --- **Moved to GitHub: https://github.com/crenshawdev/cadence/issues/99** This project's tracker is now GitHub; this repository remains the public archive. Closed here as migrated, not as resolved.
john closed this issue 2026-08-25 16:38:01 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: crenshawdev/cadence-archived#250
No description provided.