project-memory

To maintain project memory for feature slices, use the project-memory skill to create numbered feature folders, stubs, and roadmap entries before implementation begins, ensuring future work remains discoverable and consistent.

You need to track architecture decision records (ADRs) when implementation reveals recurring problems or architectural choices, ensuring resolved issues are recorded in the prescribed order for future project consistency.

To keep changelog entries and roadmap status synchronized with real work, apply the project-memory skill during slice wrap-up to manage validation artifacts and documentation updates in the prescribed order.

Yes, project-memory applies to starting or finishing non-trivial work in a repository, including specification setup, implementation coordination, and release wrap-up by tracking specs, roadmap status, and validation artifacts.

To ensure repository project hygiene for feature work, use the project-memory skill to guide required planning, implementation, and wrap-up records, keeping roadmap status, changelog entries, and documentation updates synchronized with the real state.

The best way to prevent feature work from losing project memory is to use the project-memory skill to guide required planning, implementation, and wrap-up records for each slice, ensuring specs, decisions, and release notes are captured in the right places.