Write memory-template plugin skill

jared commented

2026-06-30 15:24:19 +00:00

Owner

What to build

Create cc-os/plugins/memory/skills/memory-template/SKILL.md alongside the existing skills (memory-vault, memory-write, memory-project, memory-reorganize).

The skill handles two related workflows, routing between them based on context:

Template design — a repeatable 4-step process:

Model the consumers (who reads this type and what one action each takes; grab or construct one exemplar)
Extract the minimal body shape (2–4 sections, action-first ordering; for each section write "consumer acts differently because this is here" — no line = cut)
Draft the fillable skeleton (frontmatter block + H1 + each section as header with one-line inline instruction + abbreviated filled example)
Dogfood and cut (fill with exemplar; cut empty/padded sections; tighten ambiguous instructions; done when no empty sections and no padding)

New-type creation — full lifecycle:

Recognize the trigger (SessionEnd catch-all surfaces misfit; repeated in-session workarounds; N≥3 real instances share structure)
Collect N≥3 real examples (or construct synthetic)
Define the question frame the type answers
Follow template-design flow above
Add type definition to vault-conventions.md
Create template file in _templates/
Author first 2–3 notes using the template
Dogfood critique (baked into step 4 of design process)
Refine based on findings

Key design decisions to encode in the skill: frontmatter (summary + tags) serves scanning human and recall AI; body serves injected AI mid-task and executing human (progressive disclosure, different stopping points). One shared spine, three type-specific body shapes. Subtypes are body variants within a template, never separate templates. Anti-patterns to guard: section inflation, vague headers, body duplicating frontmatter, paper-good/practice-ignored structure, convention without its boundary, smuggling project narrative.

Acceptance criteria

SKILL.md exists at the correct path
Skill routes between template-design and new-type-creation based on context
4-step template-design process fully documented with the injection-economics filter rule
New-type-creation lifecycle documented (9 steps)
Key design decisions and anti-patterns documented
Skill is indexed in the cc-os project graph (Graphify), not the vault graph

Blocked by

Issue #1 (reconcile vault-conventions.md — templates sit on top of the frontmatter contract)

## What to build Create `cc-os/plugins/memory/skills/memory-template/SKILL.md` alongside the existing skills (`memory-vault`, `memory-write`, `memory-project`, `memory-reorganize`). The skill handles two related workflows, routing between them based on context: **Template design** — a repeatable 4-step process: 1. Model the consumers (who reads this type and what one action each takes; grab or construct one exemplar) 2. Extract the minimal body shape (2–4 sections, action-first ordering; for each section write "consumer acts differently because this is here" — no line = cut) 3. Draft the fillable skeleton (frontmatter block + H1 + each section as header with one-line inline instruction + abbreviated filled example) 4. Dogfood and cut (fill with exemplar; cut empty/padded sections; tighten ambiguous instructions; done when no empty sections and no padding) **New-type creation** — full lifecycle: 1. Recognize the trigger (SessionEnd catch-all surfaces misfit; repeated in-session workarounds; N≥3 real instances share structure) 2. Collect N≥3 real examples (or construct synthetic) 3. Define the question frame the type answers 4. Follow template-design flow above 5. Add type definition to `vault-conventions.md` 6. Create template file in `_templates/` 7. Author first 2–3 notes using the template 8. Dogfood critique (baked into step 4 of design process) 9. Refine based on findings Key design decisions to encode in the skill: frontmatter (`summary` + tags) serves scanning human and recall AI; body serves injected AI mid-task and executing human (progressive disclosure, different stopping points). One shared spine, three type-specific body shapes. Subtypes are body variants within a template, never separate templates. Anti-patterns to guard: section inflation, vague headers, body duplicating frontmatter, paper-good/practice-ignored structure, convention without its boundary, smuggling project narrative. ## Acceptance criteria - [ ] `SKILL.md` exists at the correct path - [ ] Skill routes between template-design and new-type-creation based on context - [ ] 4-step template-design process fully documented with the injection-economics filter rule - [ ] New-type-creation lifecycle documented (9 steps) - [ ] Key design decisions and anti-patterns documented - [ ] Skill is indexed in the cc-os project graph (Graphify), not the vault graph ## Blocked by - Issue #1 (reconcile vault-conventions.md — templates sit on top of the frontmatter contract)

jared referenced this issue

2026-06-30 15:24:19 +00:00

Write howto.md template #3

jared commented

2026-06-30 20:08:06 +00:00

Author

Owner

Done — created plugins/memory/skills/memory-template/SKILL.md (routes template-design ↔ new-type-creation; 4-step process + injection-economics filter; 9-step lifecycle; design decisions + 6 anti-patterns).

jared closed this issue

2026-06-30 20:08:17 +00:00

jared referenced this issue from a commit

2026-06-30 20:51:31 +00:00

Implement SB Content Plan Phase 1: memory-template skill + note templates

Write memory-template plugin skill #2

What to build

Acceptance criteria

Blocked by