Guide creation of meta-prompt templates that encode engineering workflows into reusable, scalable units. Use when creating slash commands that generate plans, designing workflow templates, or encoding team best practices into agentic prompts.
Creates reusable meta-prompt templates that encode engineering workflows into scalable units. Use when designing slash commands, workflow templates, or encoding team best practices into agentic prompts.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install google-ecosystem@melodic-softwareThis skill is limited to using the following tools:
Guide for creating meta-prompt templates - prompts that build prompts.
Every effective template has five sections:
Clear description at the top:
# [Work Type] Planning
Create a new plan in specs/*.md to resolve the [Work Type] using
the exact specified markdown Plan Format.
Guidance for the agent:
## Instructions
- You are writing a plan, not implementing
- Use your reasoning model: THINK HARD about the plan
- Focus on files in the Relevant Files section
- Include validation commands that verify completion
- Fill in every section of the Plan Format
Guide context loading:
## Relevant Files
Focus on the following files:
- README.md (project context)
- src/** (source code)
- tests/** (test patterns)
- docs/** (documentation)
Template with placeholders:
## Plan Format
# [WorkType]: <name>
## Description
<what needs to be done>
## Relevant Files
<files to modify>
## Step by Step Tasks
<numbered actionable tasks>
## Validation Commands
<commands proving completion>
## Notes
<edge cases and considerations>
Accept user input:
## [WorkType]
$ARGUMENTS
What class of problems does this template solve?
What sections does this work type need?
| Work Type | Essential Sections |
|---|---|
| Chore | Description, Files, Tasks, Validation |
| Bug | Problem, Solution, Reproduce, Root Cause, Tasks, Validation |
| Feature | User Story, Implementation Plan, Testing, Acceptance |
| Refactor | Before/After, Migration, Rollback |
Guide the agent's reasoning:
Limit scope to improve quality:
Validate your template:
Before deploying a template:
$ARGUMENTS correctlyUse your reasoning model: THINK HARD about the plan
and the steps to accomplish this work.
Create a new plan in specs/*.md using the following naming:
specs/[worktype]-[descriptive-name].md
The Validation Commands section is REQUIRED. Every plan must
include commands that prove the work is complete.
Bad: **/* (everything)
Good: src/auth/**, tests/auth/** (focused)
Bad: No way to verify completion Good: Specific test and lint commands
Bad: "Make a good plan" Good: "Focus on error handling edge cases, include rollback steps"
Bad: Plan written somewhere undefined
Good: specs/[worktype]-[name].md pattern
Date: 2025-12-26 Model: claude-opus-4-5-20251101
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.