record-project-memory

To document architectural decisions, the Skill extracts high-value insights from converged task contexts and appends them into a structured project memory file. It enforces a promotion bar to ensure only reusable, non-obvious engineering lessons are recorded for future team reference.

Maintaining a project memory file requires a curation pass that automatically deduplicates, supersedes, and prunes entries. This approach enforces strict promotion criteria to filter out trivial information, keeping your engineering knowledge base clean and focused on durable architectural insights.

You should record engineering insights after task convergence, specifically when a development task yields high-value, non-obvious lessons. Capturing durable architectural decisions at this stage ensures the knowledge is mature, validated, and genuinely reusable before entering the project memory file.

No, the project memory recording process strictly prohibits the inclusion of sensitive data or PII. It focuses exclusively on extracting durable engineering lessons and architectural best practices, ensuring your knowledge management workflow remains compliant and secure.

Yes, the curation process requires adherence to your existing project-specific memory file conventions. It operates within your established documentation structure to append, deduplicate, and supersede engineering lessons without disrupting your current knowledge management format.

Retaining obsolete practices happens without a curation pass to supersede and prune outdated entries. The Skill automatically evaluates converged task contexts to replace or remove superseded architectural lessons, ensuring your project memory file retains only currently relevant engineering best practices.