project-experience

Project Experience

Research evidence-backed lessons across the shared project-document library and maintain its compact global cache.

Boundary: ADD reads _exp_memory.md once per new Agent/session and owns each _<ProjectName>_exp.md project capsule. This skill performs explicit cross-project research or an approved global-cache refresh; it does not author project documents, project capsules, AC state, or implementation plans.

Use and skip

Use this skill when the user explicitly asks to:

• compare prior projects or find reusable cross-project lessons;
• investigate whether a past project solved a similar problem;
• refresh, rebuild, or audit _exp_memory.md;
• complete an ADD-approved global-cache refresh.

Skip it for ordinary implementation, architecture work inside one known project, Mode A/Mode B execution, small fixes, documentation edits, or a request already covered by the project's capsule. ADD remains functional when this skill is absent.

Phase 0: Locate the shared document hub

All project documents and the global experience cache live under one shared document hub ($DOC_HUB), which may be an Obsidian vault or plain directory. Use canonical absolute paths with shell/filesystem tools; when a host accepts only workspace-relative vault paths, use that supported form without changing Hub identity.

1. Read ~/.add-hub. A trimmed path naming an existing directory is authoritative.
2. If the pointer is missing or stale, search for **/_exp_memory.md under the user's home directory. Validate candidate parents by checking for hub templates and <ProjectName>/AC.md or <ProjectName>/<ProjectName>.md files.
3. If one candidate validates, use it and write ~/.add-hub. If none or multiple remain, ask the user to choose a stable shared directory.
4. For a new hub, create the directory, create an empty _exp_memory.md, and write the pointer.

Cache presence helps fallback discovery but never overrides a valid pointer or proves Hub identity by itself.