| name | project-knowledge-gardener |
| description | Use when the user wants to clean up or expand project notes, connect them to stakeholders and references, and extract reusable knowledge into 3 - Knowledge without losing project-specific context. |
Project Knowledge Gardener
Use this skill for project maintenance and cross-linking.
Goal
Keep 2 - Projects/ actionable while moving reusable lessons into 3 - Knowledge/.
Workflow
- Read the relevant project note and any linked meeting or reference notes.
- Separate content into:
- project status and decisions
- stakeholder context
- raw or supporting evidence
- reusable patterns
- Keep project-specific content in
2 - Projects/.
- Move generalized insight into
3 - Knowledge/ when it can help future work.
- Ensure the project links to:
- core stakeholders in
1 - Stakeholders/
- recent meetings in
4 - Meetings/
- supporting evidence in
5 - References/
- Remove duplication by replacing repeated blocks with links.
Heuristics
- If a note explains a pattern that applies to more than one project, it belongs in
3 - Knowledge/.
- If a note mainly tracks scope, owners, timing, or deliverables, it belongs in
2 - Projects/.
- If a note mainly captures who matters and how they relate, it belongs in
1 - Stakeholders/.
Output Style
Report:
- what stayed in the project note
- what was promoted to knowledge
- which links were added or tightened
