---
name: minimalist-fast-change
description: Use when a small, local, low-risk change has clear acceptance and does not need a full backlog, sprint, or architectural design.
---

# Minimalist Fast Change

Use this route only when the request has clear acceptance, touches a local
area, preserves existing boundaries, and has low uncertainty. Resolve the
shared template from the installed plugin root:

    <plugin-root>/templates/fast-change.md

## Decide

Confirm and record:

- one concise intent and observable acceptance criteria;
- why the change is local and low risk;
- unchanged contracts, permissions, data, and deployment boundaries;
- the smallest implementation and explicit out-of-scope items;
- the escalation trigger if the boundary or acceptance becomes unclear.

If any of these are unknown, route to minimalist-brainstorming,
minimalist-specification, or minimalist-architecture rather than guessing.

## Execute and verify

Make only the smallest change that satisfies the acceptance criteria. Record
the changed area, commands or observations used for verification, results,
unresolved limitations, and evidence in a fast-change record. Distinguish
written, checked, passing, demonstrated, and accepted; code existence alone is
not acceptance.

## Handoff

Close the route with a user-facing result, evidence, owner, and handoff
follow-up. If
the change reveals a new story, a cross-boundary decision, or more work than
the local record can explain, stop and hand off to minimalist-router. Do not
force a backlog or sprint ceremony for a genuinely trivial change, but do not
use the fast route to hide feature scope.