SKILLS_REFERENCE.md.tmpl

skills/cowork-project-architect/templates/SKILLS_REFERENCE.md.tmpl

1. ---
2. type: skills-reference
3. scope: project-root
4. tags:
5. - claude
6. - skills
7. - reference
8. created: [YYYY-MM-DD]
9. updated: [YYYY-MM-DD]
10. ---
12. <!--
13. SKILLS_REFERENCE.md: Skills relevant to this project.
15. Pull from existing user skills first. If a skill doesn't exist for a known
16. need this project will hit, flag it as a future skill to build at the bottom.
18. Don't list every skill in the user's library, only the ones genuinely
19. relevant to this project's work.
20. -->
22. # [PROJECT NAME]: Skills Reference
24. Skills that apply to this project's work. Each entry includes trigger phrases and any project-specific overrides.
26. ## Active skills
28. ### [skill-name]
30. **Location:** `[path to SKILL.md]`
32. **Why it applies:** [One sentence on the connection between this skill and this project's work.]
34. **Trigger phrases in this project:** [Phrases the user will likely use that should activate this skill.]
36. **Project-specific overrides:** [Any way this project changes how the skill should behave. If none, write "None."]
38. ---
40. ### [skill-name]
42. [Same structure.]
44. ---
46. ## Skills to build (gaps)
48. <!-- Things this project will hit that don't have a skill yet. Each entry is
49. a one-line description of what the skill should do. These can later be
50. turned into real skills. -->
52. - **[Proposed skill name]:** [What it should do. When it should trigger.]
53. - **[Proposed skill name]:** [What it should do.]
55. ## Skill priority within this project
57. When multiple skills could apply, prefer them in this order:
58. 1. [Most project-specific skill]
59. 2. [Next]
60. 3. [Most general]
62. [One sentence on why this ordering, e.g., "Project-specific skills win because they encode constraints the general skills don't know about."]
64. ## Cross-references
66. - Model assignments per skill: [[MODEL_GUIDE]]
67. - Sub-agent integration: [[SUBAGENTS]]