Superior Docs

Build documentation that lets a future maintainer recover the project's current shape, important decisions, and safe operating procedures without relying on chat history. Documentation is a maintained view of evidence, not a second source of invented truth.

Select the mode

• Bootstrap: establish a useful docs/ system where none exists.
• Record: capture a verified implementation, fix, refactor, configuration change, or feature outcome in the implementation timeline.
• Synchronize: update affected documents after verified project changes.
• Reconstruct: derive architectural evolution, releases, or maintenance history from repository evidence.
• Handoff: capture the current implementation, boundaries, risks, and next work at the end of a substantial effort.

Do not ask the user to choose when the request already determines the mode.

Record implementation work by default

After verified material changes to code, configuration, schema, API behavior, security controls, build behavior, or user-visible functionality, create or update an implementation record unless the user explicitly asks not to create or update documentation.

Read references/automatic-change-recording.md whenever another implementation skill completes material work. It defines the default path, minimum bootstrap, entry schema, opt-out behavior, and exclusions.