hs:remember

Captures session decisions, learnings, and feedback into durable registers after human approval.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/Dozyboy/VSF --skill hs-remember-dozyboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hs:remember
Source: https://github.com/Dozyboy/VSF/tree/main/Day2_VSF/Demo1/harness/plugins/hs/skills/remember
Command: npx skills add https://github.com/Dozyboy/VSF --skill hs-remember-dozyboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable knowledge from a working session — architectural decisions, non-obvious learnings, user feedback, diagnosed failures — is easily lost when the session ends. This Skill reviews the recent session, identifies what is worth keeping, and writes each approved item to the correct durable home so nothing has to be rediscovered later. ## Core Features & Use Cases - Evidence-anchored capture: Reviews recent turns (and an optional --since <git-ref> diff) and proposes candidates with file:line, ID, or quote evidence — never fabricated. - One fact, one home: Routes each item to the right destination — decisions to docs/decisions.md via decision_register.py, facts and feedback to auto-memory files with a MEMORY.md pointer, deferred work to docs/backlog.yaml, repeatable failures to harness/LESSONS.md, and coined terms to docs/glossary.yaml. - Human-in-the-loop writes: Presents a numbered proposal list and writes only what the user approves; it never auto-writes a decision, gate config, or enforcement rule. - Governed decision flips: Replacing an existing DEC triggers a blast-radius scan (--scan-flip), and cross-scope flips require explicit user confirmation via a confirm token before the register is updated. - Use Case: After settling on a retry threshold and fixing a recurring wiring bug during a session, invoke this Skill to record the threshold as a DEC, log the bug pattern in LESSONS.md, and capture the user's correction as a feedback memory — each approved individually. ## Quick Start Ask the assistant to run the remember skill to review this session and propose durable entries for the decisions and lessons we just made.

Frequently Asked Questions about hs:remember

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

FAQPage Schema
How do I record an architectural decision from a coding session?▼

Invoke the remember skill after making a decision; it reviews the recent session, proposes a DEC entry with evidence, and writes it to docs/decisions.md through decision_register.py only after you approve. Nothing is written automatically.

How do I replace or supersede an existing decision entry?▼

Run the skill with the flip flow: it first runs decision_register.py --scan-flip DEC-n to check the blast radius. If cross-scope neighbors exist, you must explicitly approve via a confirmation step before the flip is written with --supersedes.

Where does captured knowledge get stored?▼

Each fact type has one home: decisions go to docs/decisions.md, durable facts and feedback go to the session auto-memory directory with a MEMORY.md pointer, deferred work goes to docs/backlog.yaml, repeatable failures go to harness/LESSONS.md, and coined terms go to docs/glossary.yaml.

Does the remember skill write anything without my approval?▼

No. The skill only reviews, classifies, and proposes entries as a numbered list. You choose all, some, none, or edited versions, and only approved entries are written through their designated register scripts.

Can this skill create enforcement rules from a captured lesson?▼

No. When a lesson is rule-worthy, the skill records the memory or lesson and proposes a handoff to the hs:rule-author skill, which authors enforcement rules. The remember skill never edits rule or gate-config files itself.