documentation-reseed
Documentation Reseed
Use this when a repository needs a full documentation reset. For routine updates, use documentation-maintenance.
Principle
Reseed the documentation system, not just the files. Old prose and old locations are evidence, not truth. Current code, local rules, generated sources, and verified runtime behavior are the source of truth.
Clear ordinary docs out of the way so the old structure stops shaping the new one. Preserve only durable context that future agents cannot safely recover from code alone.
Related Skills
- Use
documentation-maintenancefor write/delete/keep rules, source-of-truth choices, docs-as-code handling, semantic rewrite guards, and final-response shape.
If documentation-maintenance is unavailable, continue with the same principles and note the gap in the final report.
Reseed Workspace
For a new run, default to .scratch/documentation-reseed/YYYY-MM-DD/, using the current date. Before creating it, inspect existing reseed workspaces. An incomplete workspace has status active or awaiting-continuation. Use the workspace the user identifies; when the request is to continue an existing reseed and exactly one incomplete workspace exists, use it. Ask when multiple incomplete workspaces exist or when starting new versus resuming is unclear. Append -N only for a genuinely new run.