post-it

Manage temporary working memory notes across AI project sessions.

7|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dmlguq456/agent_setting --skill post-it
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-it
Source: https://github.com/dmlguq456/agent_setting/tree/main/adapters/claude/skills/post-it
Command: npx skills add https://github.com/dmlguq456/agent_setting --skill post-it

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents important project context, decisions, and next steps from being lost between AI sessions by maintaining a lightweight working memory layer.

Core Features & Use Cases

  • Working Memory Management: Capture, review, resolve, and prune temporary project notes while keeping permanent records in artifacts and structured profiles.
  • Session Handoff Support: Summarize ongoing work, decisions, blockers, and next actions so future sessions can continue efficiently.
  • Scoped Context Storage: Separate project-specific notes from reusable user-level preferences and promote stable information into structured memory.
  • Use Case: When a long development or research task spans multiple sessions, use this Skill to preserve active threads, decisions, and handoff details without maintaining manual notes.

Quick Start

Use the post-it skill to save the current project decisions and create a concise handoff summary for the next session.

Frequently Asked Questions about post-it

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

FAQPage Schema
How do I preserve project context and decisions across AI sessions?

To preserve project context across AI sessions, use a working memory management layer to capture active threads, decisions, and handoff details. This prevents important information from being lost between interactions by maintaining temporary notes and structured records.

What is the best way to create a session handoff summary for ongoing work?

Creating a session handoff summary involves capturing ongoing work, decisions, blockers, and next actions into scoped notes. This approach ensures future sessions can continue efficiently without needing manual notes or replaying previous conversation history.

How does working memory management separate temporary project notes from permanent records?

Working memory management separates temporary project notes from permanent records by keeping active threads in a lightweight layer while storing stable information in artifacts and structured profiles. Scoped context storage ensures project-specific notes remain distinct from user-level preferences.

When do I need to use scoped notes for cross-session workflow continuity?

You need scoped notes for cross-session workflow continuity when a long development or research task spans multiple interactions. This approach preserves active threads and evolving tasks without maintaining manual notes or losing context between sessions.

How do I prune temporary project notes without losing important memory records?

To prune temporary project notes without losing important records, apply lifecycle handling and confirmation rules during memory cleanup. This ensures active threads are resolved appropriately while stable information is promoted into permanent structured memory profiles.

Can I use session continuity notes for both project workflows and user preferences?

Yes, session continuity notes support both project workflows and user preferences by separating project-specific context from reusable user-level settings. Stable information from either scope can be promoted into structured memory for future use.