figure-it-out git:20261025.251cd2eA

Immutable. This exact content never changes and is served at /api/v1/blob/888fb7fe39a87aaf.

---
name: figure-it-out
description: "Plan and execute an authorized large migration or cross-cutting task with measurable completion criteria and a concise evidence trail."
---

# Figure it out

Follow the consuming project's instructions and requested scope; use the
[portable defaults](../orbyn-workflow/references/project-policy.md) only where guidance is missing.

Use [orbyn-plan](../orbyn-plan/SKILL.md) to establish or revise the execution plan
and [stack ownership](../orbyn-workflow/references/project-policy.md#stack-and-ownership) to place changes.

Define a checkable end state, exclusions and the largest unresolved risk. Inventory
the actual units before planning. Sequence by dependency and risk, using coherent
units that can be inspected without leaving ambiguous ownership.

Choose evidence and reversible recovery for each unit. Use existing tools before
building automation; create a small reusable helper when repetition or reliable
checking justifies it. Follow the user's verification scope.

For each unit, the lead states the hypothesis and throughput checkpoint, delegates
substantial investigation/implementation with owned files, inspects the actual
artifact and diff, and performs authorized verification. Follow the
[workflow lead contract](../orbyn-workflow/SKILL.md); keep coupled code with one
owner and no more than two active children. Route corrections to the same owner.
A child executes its owned unit directly without delegation. Retain useful
evidence and correct disproven assumptions; do not repeat an unchanged failed
attempt without a new explanation.

Use [show-me-your-work](../show-me-your-work/SKILL.md) for decisions that matter
later. Revisit the full checklist at the end. Report verified, unverified and
blocked parts without silently reducing the requested outcome.

## Finish the vertical slice

For an API extraction, the inventory includes shared schema, consumers, persistence, service routing and the old handler. Close a unit only when its named artifact and evidence exist. Keep unfinished operator/deployment work visible; do not replace it with a future-work paragraph and call the migration complete.

## Operational method

Use the [local operating method](references/operating-method.md) for the execution
sequence, concrete failure case, expected result and stopping condition. It is
Orbyn-authored guidance; historical source notices remain in provenance.