memory-record

You can persist project decisions by saving structured context and rationale into local memory files. This captures non-derivable information generated during skill execution, ensuring durable cross-session recall and preventing knowledge loss.

Tracking design rationale is best achieved by saving decision context into long-term knowledge storage. This specifically captures insights generated during command executions, allowing future sessions to reference why specific architectural choices were made.

Yes, this memory persistence mechanism operates within the Spec Kit ecosystem. It captures contextual insights during command or skill executions, requiring a valid source trigger and scope definition to maintain an organized index of project knowledge.

You need to record project context whenever non-derivable information is generated, such as switching from a REST API to GraphQL during planning. It captures review outcomes and user preferences that cannot be automatically derived from the codebase.

Yes, you can save notes into either short-term session memory or long-term knowledge storage. This durable persistence mechanism lets you choose the appropriate retention scope based on whether the context is needed temporarily or for future cross-session reference.

Capturing decision tracking requires a source trigger and scope definition to maintain an organized index of project knowledge. This structure ensures non-derivable context is properly categorized and efficiently retrieved during future command or skill executions.