remember

Classify session findings and route them to project memory, notepad, or durable docs.

1|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Cheggin/request-for-startups --skill remember-cheggin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remember
Source: https://github.com/Cheggin/request-for-startups/tree/main/skills/remember
Command: npx skills add https://github.com/Cheggin/request-for-startups --skill remember-cheggin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs to avoid losing valuable context and to speed up future work.

Core Features & Use Cases

  • Classify session findings into durable, temporary, or procedural memories.
  • Route items to the correct surface (project memory, notepad priority, notepad working, or docs) and update surfaces without duplicating content.
  • Flag duplicates or conflicts for cleanup and consistency.

Quick Start

Classify each knowledge item encountered in a session and store it in the correct memory surface for quick recall and durable accessibility.

Frequently Asked Questions about remember

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize session findings into durable project memory?

To organize session findings into durable project memory, classify each item as durable, temporary, or procedural, then route it to the correct surface like project memory, notepad, or docs for quick recall and consistency.

What is the best way to classify knowledge items during an ongoing product or engineering session?

The best way to classify knowledge items is to evaluate their longevity and actionability, sorting them into durable, temporary, or procedural categories before writing updates to the appropriate memory surface without duplicating content.

How do I route decisions to a notepad or durable docs without creating duplicates?

Routing decisions to a notepad or durable docs without duplicates requires classifying the item, proposing a destination, and writing the update while the system flags existing duplicates or conflicts for cleanup and consistency.

Can I use knowledge-management routing for ongoing research and documentation tasks?

Yes, you can use knowledge-management routing for ongoing research, decision-making, and documentation tasks by gathering findings, classifying them, and storing them in the correct memory surface for durable accessibility.

How do I flag conflicts when updating multiple project memory surfaces?

To flag conflicts when updating multiple project memory surfaces, route items to their destinations and let the classification workflow detect duplicates or conflicting information, ensuring consistency and speeding up future work.

Why does project knowledge get lost across product, design, and engineering team sessions?

Project knowledge gets lost across team sessions when findings are not classified into durable, temporary, or procedural memories and routed to appropriate surfaces like project memory, notepad, or durable docs for accessible recall.