Skip to main content

Playbook Method Template

What makes a method repeatable?

A playbook page helps a reader do one repeatable job.

Use this when the page job is playbook.

Frontmatter​

type: playbook
template: playbook-method-template
template_url: /playbook/standards/templates/playbook-method-template
loop_phase: action
level: working

Shape​

  1. Name the outcome.
  2. List inputs and preconditions.
  3. Give ordered steps.
  4. Name the output of each step.
  5. Add checks and gates.
  6. Show proof of done.

Skeleton​

TITLE

This method produces OUTCOME.

## Inputs

- Input A
- Input B

## Steps

1. Do the first action.
2. Produce the first output.
3. Check the output.

## Checks

- What must be true before moving on?

## Failure Modes

- What usually breaks?

## Proof Of Done

What evidence shows the method worked?

## Context

- [Related standard](/playbook/)

Checks​

  • The page drives action instead of teaching theory.
  • Each step has an output.
  • The proof of done is visible.
  • Failure modes are specific enough to catch bad execution.

Failure Modes​

  • The page explains why for too long before the first action.
  • Steps are vague and produce no artifact.
  • Checks depend on taste instead of evidence.

Context​

Questions​

What should a new operator produce after following this page?

  • What input starts the method?
  • What artifact or state proves each step worked?
  • Which check stops bad work before it compounds?