david.delagneau
dbc1894e27
- Introduced new maps for navigating project knowledge, including "Current Work," "Fidelity Domain," "Fidelity Apps," "Work Items," and "People." - Created base files for daily notes, decisions, people, systems, work items, and workstreams with defined properties and views. - Developed templates for daily notes, decisions, meeting notes, persons, systems, work items, and workstreams to standardize documentation. - Updated scripts and prompts to reflect the new project-knowledge directory structure. - Removed outdated onboarding and start-here documents, consolidating relevant information into the new maps. - Ensured all references in workflows and scripts point to the new project-knowledge paths.
1.1 KiB
1.1 KiB
description
| description |
|---|
| Create a canonical memory note using the project-agnostic memory interface |
Create a new canonical memory note from a known type.
Supported types:
dailywork-itempersondecisionsystemworkstreammeeting-note
User request:
$ARGUMENTS
Read:
@core/integrations/memory-vault-model.md @agent-memory/workflows/workspace-architecture.md @project-knowledge/09-templates/work-item.md @project-knowledge/09-templates/person.md @project-knowledge/09-templates/decision.md @project-knowledge/09-templates/system.md @project-knowledge/09-templates/workstream.md
Instructions:
- Parse the requested type, slug, and title from
$ARGUMENTS. - Use
bash scripts/memory/memory.sh create <type> <slug> [title]when type and slug are clear. - If type or slug is not clear, do not guess. Explain the expected format.
- After creation, inspect the generated file and update metadata/content if the user provided enough context.
- Keep the note in the canonical folder selected by the memory interface.
Return:
- Created file
- Any metadata/content refined
- Any missing details the user may want to add