mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-06-26 12:23:01 +02:00
Kieran Klaassen
4b0f058f2c
Based on PR feedback that 14 commands in core was too many: - **compound-engineering-core** (14 agents, 4 commands, 5 skills) - Only 4 workflow commands: /workflows:plan, /workflows:review, /workflows:work, /workflows:compound - All code review agents stay in core (referenced by /workflows:review) - **workflow-automation** (3 agents, 7 commands, 1 skill) - NEW - /resolve_pr_parallel, /plan_review, /resolve_parallel, /resolve_todo_parallel - /reproduce-bug, /triage, /changelog - bug-reproduction-validator, pr-comment-resolver, every-style-editor agents - **plugin-dev** (3 commands, 2 skills) - NEW - /generate_command, /heal-skill, /create-agent-skill - skill-creator, create-agent-skills skills All READMEs updated with "Works Best With" philosophy emphasizing that core provides the foundation but real power comes from combining plugins. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.2 KiB
2.2 KiB
Workflow: Add a Reference to Existing Skill
<required_reading> Read these reference files NOW:
- references/recommended-structure.md
- references/skill-structure.md </required_reading>
ls ~/.claude/skills/
Present numbered list, ask: "Which skill needs a new reference?"
Step 2: Analyze Current Structure
cat ~/.claude/skills/{skill-name}/SKILL.md
ls ~/.claude/skills/{skill-name}/references/ 2>/dev/null
Determine:
- Has references/ folder? → Good, can add directly
- Simple skill? → May need to create references/ first
- What references exist? → Understand the knowledge landscape
Report current references to user.
Step 3: Gather Reference Requirements
Ask:
- What knowledge should this reference contain?
- Which workflows will use it?
- Is this reusable across workflows or specific to one?
If specific to one workflow → Consider putting it inline in that workflow instead.
Step 4: Create the Reference File
Create references/{reference-name}.md:
Use semantic XML tags to structure the content:
<overview>
Brief description of what this reference covers
</overview>
<patterns>
## Common Patterns
[Reusable patterns, examples, code snippets]
</patterns>
<guidelines>
## Guidelines
[Best practices, rules, constraints]
</guidelines>
<examples>
## Examples
[Concrete examples with explanation]
</examples>
Step 5: Update SKILL.md
Add the new reference to <reference_index>:
**Category:** existing.md, new-reference.md
Step 6: Update Workflows That Need It
For each workflow that should use this reference:
- Read the workflow file
- Add to its
<required_reading>section - Verify the workflow still makes sense with this addition
Step 7: Verify
- Reference file exists and is well-structured
- Reference is in SKILL.md reference_index
- Relevant workflows have it in required_reading
- No broken references
<success_criteria> Reference addition is complete when:
- Reference file created with useful content
- Added to reference_index in SKILL.md
- Relevant workflows updated to read it
- Content is reusable (not workflow-specific) </success_criteria>