Write reusable prompts including system prompts, workflow prompts, delegation prompts, and meta prompts. Use when creating commands, automating workflows, making tasks reusable, or when the user says "write a prompt", "create a command", or "automate this".
The prompt is the fundamental unit of automation. A good prompt becomes a durable multiplier for you, your team, and the agents that will execute it later.
Design every prompt for three audiences:
Consistency beats complexity. Reuse the same format unless a real constraint forces something different.
Ask for the task you want to automate:
"Create a prompt that reviews my code changes before commit"
Identify the lowest level that solves the job, then write the prompt with only the sections it needs.
Use this skill when the task is to create or refine a reusable prompt, such as:
Strong trigger signals:
Most real work happens at Levels 2 to 4.
| Level | Name | Capability | When to Use |
|---|---|---|---|
| 1 | High-Level | Static, ad hoc prompt | Simple repeated tasks |
| 2 | Workflow | Sequential steps | Multi-step execution |
| 3 | Control Flow | Branching and loops | Validation, iteration, conditions |
| 4 | Delegation | Agent orchestration | Parallel work or specialized sub-agents |
| 5 | Higher-Order | Prompt consumes another prompt or plan | Plan -> Build -> Review chains |
| 6 | Template Meta | Prompt creates prompts | Scaling prompt creation |
| 7 | Self-Improving | Expertise accumulates | Domain experts that learn over time |
Read the reference that matches the prompt you are building:
Sections are modular. Use only what the prompt actually needs.
| Section | Purpose | Usefulness | Difficulty |
|---|---|---|---|
| Workflow | Step-by-step execution play | S-tier | C-tier |
| Variables | Dynamic and static inputs | A-tier | B-tier |
| Examples | Show desired behavior | A-tier | C-tier |
| Report | Output format specification | B-tier | C-tier |
| Purpose | High-level description | B-tier | D-tier |
| Instructions | Guardrails and constraints | B-tier | C-tier |
| Template | Exact format for meta-prompts | A-tier | A-tier |
| Expertise | Durable knowledge for self-improving prompts | A-tier | S-tier |
| Metadata | Discovery, tool hints, invocation shape | C-tier | C-tier |
| Codebase Structure | File and module map | C-tier | C-tier |
| Relevant Files | Specific file references | C-tier | C-tier |
Defaults:
Most strong prompts follow this shape:
INPUT
- variables
- context
WORKFLOW
- ordered execution steps
- control flow where needed
- delegation where useful
OUTPUT
- report format
- artifacts created
Input and output help humans scan the prompt quickly. Workflow is where the real execution logic lives.
System or developer prompts:
Task or workflow prompts:
When writing a reusable prompt, default to a simple markdown structure like this unless the target environment requires a different format:
---