template-engineering

# Template Engineering

Guide for creating meta-prompt templates - prompts that build prompts.

## When to Use

- Creating new slash commands that generate plans
- Encoding team workflows into reusable templates
- Designing meta-prompts for chores, bugs, features
- Analyzing existing templates for improvement

## Template Anatomy

Every effective template has five sections:

### 1. Purpose Section

Clear description at the top:

```markdown
# [Work Type] Planning

Create a new plan in specs/*.md to resolve the [Work Type] using
the exact specified markdown Plan Format.
```

### 2. Instructions Section

Guidance for the agent:

```markdown
## 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
```

### 3. Relevant Files Section

Guide context loading:

```markdown
## Relevant Files

Focus on the following files:
- README.md (project context)
- src/** (source code)
- tests/** (test patterns)
- docs/** (documentation)
```

### 4. Plan Format Section

Template with placeholders:

```markdown
## 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>
```

### 5. Parameter Section

Accept user input:

```markdown
## [WorkType]
$ARGUMENTS
```

## Design Workflow

### Step 1: Identify the Work Type

What class of problems does this template solve?

- Chores: Maintenance, updates, cleanup
- Bugs: Investigation and fixes
- Features: New functionality
- Refactors: Code improvement

### Step 2: Define the Plan Structure

What sections does this work type need?

| Work Type | Essential Sections |
| --- | --- |
| Chore | Description, Files, Tasks, Validation |
| Bug | Problem, Soluti