8cc99ab483
Major restructure of the compounding-engineering plugin: ## Agents (24 total, now categorized) - review/ (10): architecture-strategist, code-simplicity-reviewer, data-integrity-guardian, dhh-rails-reviewer, kieran-rails-reviewer, kieran-python-reviewer, kieran-typescript-reviewer, pattern-recognition-specialist, performance-oracle, security-sentinel - research/ (4): best-practices-researcher, framework-docs-researcher, git-history-analyzer, repo-research-analyst - design/ (3): design-implementation-reviewer, design-iterator, figma-design-sync - workflow/ (6): bug-reproduction-validator, every-style-editor, feedback-codifier, lint, pr-comment-resolver, spec-flow-analyzer - docs/ (1): ankane-readme-writer ## Commands (15 total) - Moved workflow commands to commands/workflows/ subdirectory - Added: changelog, create-agent-skill, heal-skill, plan_review, prime, reproduce-bug, resolve_parallel, resolve_pr_parallel ## Skills (11 total) - Added: andrew-kane-gem-writer, codify-docs, create-agent-skills, dhh-ruby-style, dspy-ruby, every-style-editor, file-todos, frontend-design, git-worktree, skill-creator - Kept: gemini-imagegen 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
75 lines
1.9 KiB
Markdown
75 lines
1.9 KiB
Markdown
# Workflow: Add a Template to a Skill
|
|
|
|
<required_reading>
|
|
**Read these reference files NOW:**
|
|
1. references/using-templates.md
|
|
</required_reading>
|
|
|
|
<process>
|
|
## Step 1: Identify the Skill
|
|
|
|
Ask (if not already provided):
|
|
- Which skill needs a template?
|
|
- What output does this template structure?
|
|
|
|
## Step 2: Analyze Template Need
|
|
|
|
Confirm this is a good template candidate:
|
|
- [ ] Output has consistent structure across uses
|
|
- [ ] Structure matters more than creative generation
|
|
- [ ] Filling placeholders is more reliable than blank-page generation
|
|
|
|
If not a good fit, suggest alternatives (workflow guidance, reference examples).
|
|
|
|
## Step 3: Create Templates Directory
|
|
|
|
```bash
|
|
mkdir -p ~/.claude/skills/{skill-name}/templates
|
|
```
|
|
|
|
## Step 4: Design Template Structure
|
|
|
|
Gather requirements:
|
|
- What sections does the output need?
|
|
- What information varies between uses? (→ placeholders)
|
|
- What stays constant? (→ static structure)
|
|
|
|
## Step 5: Write Template File
|
|
|
|
Create `templates/{template-name}.md` with:
|
|
- Clear section markers
|
|
- `{{PLACEHOLDER}}` syntax for variable content
|
|
- Brief inline guidance where helpful
|
|
- Minimal example content
|
|
|
|
## Step 6: Update Workflow to Use Template
|
|
|
|
Find the workflow that produces this output. Add:
|
|
```xml
|
|
<process>
|
|
...
|
|
N. Read `templates/{template-name}.md`
|
|
N+1. Copy template structure
|
|
N+2. Fill each placeholder based on gathered context
|
|
...
|
|
</process>
|
|
```
|
|
|
|
## Step 7: Test
|
|
|
|
Invoke the skill workflow and verify:
|
|
- Template is read at the right step
|
|
- All placeholders get filled appropriately
|
|
- Output structure matches template
|
|
- No placeholders left unfilled
|
|
</process>
|
|
|
|
<success_criteria>
|
|
Template is complete when:
|
|
- [ ] templates/ directory exists
|
|
- [ ] Template file has clear structure with placeholders
|
|
- [ ] At least one workflow references the template
|
|
- [ ] Workflow instructions explain when/how to use template
|
|
- [ ] Tested with real invocation
|
|
</success_criteria>
|