Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From project-knowledge
Routes project knowledge to the right store. Use when deciding where to put information, looking up existing knowledge, or understanding the relationship between specs, notes, decisions, journal entries, and docs. Triggers on: "where should I put this", "where do I find", "knowledge", "documentation strategy", "what goes where".
npx claudepluginhub a3lem/my-claude-plugins --plugin project-knowledgeHow this skill is triggered — by the user, by Claude, or both
Slash command
/project-knowledge:project-knowledgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A routing guide for project knowledge. Each store has a different contract strength and purpose.
Captures decisions, conventions, patterns, issues, and concepts from conversations into docs/ markdown nodes using triage output. Auto-activates on save intents or decision signals.
Guides active use of .claude/wiki/ for recording coding patterns, gotchas, decisions via MCP tools (wiki-write, wiki-search, wiki-index). Triggers on wiki, knowledge page, pattern/gotcha/decision record requests.
Manage a per-project .briefing/ knowledge base with Obsidian-compatible Markdown notes for sessions, decisions, learnings, and references.
Share bugs, ideas, or general feedback.
A routing guide for project knowledge. Each store has a different contract strength and purpose.
| Store | Location | Contract | Purpose |
|---|---|---|---|
| Specs (reference) | specs/reference/ | Strongest | Source of truth for behavior. Gherkin scenarios. Verified before shipping. |
| Specs (changes) | specs/changes/ | Provisional | Proposed changes not yet shipped. Intent, not truth. |
| Docs | docs/ | Strong | Durable reference content. Maintained, authoritative, human-reviewed. |
| Decisions | notes/DECISIONS.md | Medium | Concise record of what was decided. One-liners with dcn-xxxx codes. |
| Notes | notes/ | Weak | Working knowledge, scratch pages, topic clusters. May go stale. |
| Journal | notes/journal/ | Weakest | Timestamped snapshots. Capture a moment. Decay over time. |
| What you have | Where it goes |
|---|---|
| Behavioral requirement with testable scenarios | specs/ (reference or change spec) |
| Durable reference that should stay current | docs/ |
| "We decided to use X instead of Y" | notes/DECISIONS.md |
| Working notes, research, topic exploration | notes/ |
| Observation, discovery, gotcha, lesson learned | notes/journal/ |
| Implementation plan for a feature | specs/changes/NNN-slug/ |
| API documentation, user guide | docs/ |
| Design rationale for a specific change | specs/changes/NNN-slug/design.md |
| Looking for | Check |
|---|---|
| How something should work | specs/reference/ first, then docs/ |
| Why a decision was made | notes/DECISIONS.md, then specs/changes/archive/ |
| Current project conventions | CLAUDE.md, docs/ |
| Recent observations or discoveries | notes/journal/ |
| Working knowledge on a topic | notes/, then notes/journal/ |
| History of a feature change | specs/changes/archive/ |
Knowledge flows upward in contract strength:
journal → notes → docs
↑
journal → notes → specs/reference/
notes/ or docs/docs/specs/specs/reference/, archive the changeThis plugin provides routing guidance. The actual stores are managed by:
| Store | Plugin |
|---|---|
specs/ | spec-driven-dev – structured workflow with proposals, Gherkin specs, design, and archive |
notes/, notes/journal/, notes/DECISIONS.md | project-notes – conventions for notes, journal entries, and decision log |
docs/ | No plugin needed – standard project documentation |
[[wikilinks]] or relative markdown links.docs/, it should be current and maintained.