# Workflow map

## Plan

| Situation | Use |
|---|---|
| Current conversation should become a spec | `to-spec` |
| Spec/plan needs tracer-bullet tickets | `to-tickets` |
| Plan needs pressure-testing | `grill-with-docs` or `grilling` |
| Domain language is fuzzy | `domain-modeling` |
| UI/state/design is uncertain | `prototype` |

## Build or fix

| Situation | Use |
|---|---|
| Failure is unclear | `diagnosing-bugs` |
| Behavior change is clear | `tdd` |
| Implementation risks unnecessary complexity | `ponytail` |
| Need worktree/branch help | `worktrunk` |

## Review

| Situation | Use |
|---|---|
| Strict maintainability review | `thermo-nuclear-code-quality-review` |
| Diff needs an over-engineering delete-list | `ponytail-review` |
| Whole repository needs a complexity audit | `ponytail-audit` |
| Deliberate simplifications need a debt ledger | `ponytail-debt` |
| Architecture feels tangled | `improve-codebase-architecture` |
| Need reusable module/interface vocabulary | `codebase-design` |
| Need a visual explanation | `plannotator-visual-explainer` |

## Communicate

| Situation | Use |
|---|---|
| Docs work | `documentation-system` |
| Skill authoring | `writing-great-skills` |
| Commit message | `caveman-commit` |
| Very concise responses | `caveman` |
| Continue in another session | `handoff` |

## Release

| Situation | Use |
|---|---|
| Changelog, version choice, release validation | `release-prep` |

## Extend

| Situation | Use |
|---|---|
| Need a workflow this repo does not include | `find-skills` |