# Template: Step File

Standard template for a progressive step loading step file.

## Generated step file format:

```yaml
---
name: step-{{NUMBER}}-{{NAME}}
description: {{DESCRIPTION}}
{{#if NEXT_STEP}}
next_step: steps/step-{{NEXT_NUMBER}}-{{NEXT_NAME}}.md
{{/if}}
---

# Step {{N}}: {{TITLE}}

## MANDATORY EXECUTION RULES:
- {{RULE_1}}
- {{RULE_2}}
- FORBIDDEN to proceed to next step until this step is complete

## YOUR TASK:
{{TASK_DESCRIPTION}}

---

## EXECUTION SEQUENCE:

### 1. {{SUBTASK_1_TITLE}}
{{SUBTASK_1_INSTRUCTIONS}}

### 2. {{SUBTASK_2_TITLE}}
{{SUBTASK_2_INSTRUCTIONS}}

### 3. Show Summary
Display step results in compact format (table preferred).

---

## SUCCESS METRICS:
- {{METRIC_1}}
- {{METRIC_2}}
- Output is compact and scannable

## NEXT STEP:
{{#if NEXT_STEP}}
After showing summary, proceed directly to `./step-{{NEXT_NUMBER}}-{{NEXT_NAME}}.md`
{{else}}
This is the final step. Skill execution is complete.
{{/if}}
```

## Step Types:

### Init Step (step-00)
- Parse arguments and flags
- Validate required inputs
- Initialize state variables
- Show configuration summary

### Analysis Step
- Read files, search codebase
- Extract patterns and information
- Show findings summary

### Generation Step
- Use templates or references
- Create/modify files
- Show what was generated

### Validation Step (usually last)
- Check generated output
- Verify conventions
- Display final summary and next steps

## Rules:
- Each step MUST be self-contained (loadable independently)
- State variables persist via conversation context
- Always show compact summary before proceeding
- Always reference next step at the end
- Last step must NOT have next_step in frontmatter
