| name | merge_projects |
| description | Identify overlapping projects and merge them into consolidated notes |
🔀 Merge Projects Skill
Detect overlapping or closely related projects and merge them into a single consolidated project note.
CRITICAL RULES
- Never merge automatically — always present candidates and get user approval
- Never delete source projects until merged project is verified
- Merged project inherits the highest status of its sources (seed < idea < active < writing < finished)
- All paper links from source projects must be preserved in merged project
- All MOC links from source projects must be preserved in merged project
- Bidirectional links must be updated: papers that linked to old projects must link to merged project
- Vault index must be updated after merge
WORKFLOW
1. Choose mode
Ask user:
- Scan for candidates? (analyze all projects for overlap)
- Merge specific projects? (user names 2-3 projects to merge)
2a. Scan mode — Identify merge candidates
Read vault index to get all projects and their descriptions.
For each project pair, assess overlap signals:
- Similar research questions or hypotheses
- Shared relevant papers (≥2 papers in common)
- Overlapping MOC links
- Complementary seed ideas (one project's approach is another's variant)
- Same phenomenon studied from slightly different angles
Score overlap:
- 🔴 High overlap (likely should merge): same core question, ≥3 shared papers, nearly identical hypotheses