unwind

Use after unwind:uw-plan to EXECUTE the rebuild — interview the user about scope/order/target, dispatch technology-agnostic per-layer builder agents that reproduce the [MUST] contracts in the target stack, hold rebuild state in a local file, and maintain a source→target verification graph that measures completeness. Supports a loop-until-verified mode.

Use to visually explore the rebuild knowledge graph. Builds and launches the Unwind dashboard (React + React Flow + ELK) pointed at docs/unwind/rebuild-graph.json with coverage, priority, and contract views.

Optional. Publish the Unwind dashboard to the scanned project's GitHub Pages gh-pages branch so it's viewable at https://<owner>.github.io/<repo>/unwind/. Builds the dashboard at the correct sub-path and commits it into an `unwind/` subdir — never blatting an existing gh-pages branch. Confirms the target, then pushes.

Use when dispatched by unwind:uw-build to rebuild ONE layer/slice of a codebase in the target stack. Technology-agnostic builder that reproduces the layer's [MUST] contracts (API surface, data model, business rules) as idiomatic target-stack code and records the source→target mapping for verification.

Use when starting any reverse engineering task - establishes how to find and use Unwind skills for codebase analysis, service mapping, and documentation

Use after layer analysis is complete to interview the user about the rebuild strategy (target stack, what to keep vs rebuild, phasing, risk) and generate a data-grounded REBUILD-PLAN.md that records those decisions.

Start here. The entry point for reverse-engineering a codebase with Unwind — orients you, checks prerequisites, handles restart vs update, then runs the rebuild pipeline (scan → analyze → plan → dashboard) with a checkpoint at each phase. Use when beginning Unwind on a repo, or when unsure which uw- skill to run first.

Use when analyzing build/dependency config, runtime configuration, program entrypoints, and deployment/ops assets the rebuild must reproduce

Use after unwind:uw-scan to orchestrate layer-by-layer analysis using specialist subagents

Use after uw-verify to fix all gaps found. Reads gaps.md and adds missing documentation.

Use after scanning (and ideally coverage verification) to emit the rebuild knowledge-graph artifact. Joins the manifest, coverage diff, and layer docs into docs/unwind/rebuild-graph.json for the dashboard.

Use when starting reverse engineering on an unfamiliar codebase to identify layers, patterns, and structure before detailed analysis

Use after layer analysis to detect gaps in documentation. Runs a deterministic coverage diff and outputs a work list for uw-complete.

Use when analyzing the database layer including schema, migrations, ORM configuration, and data access patterns

Use when analyzing REST/GraphQL API endpoints, contracts, authentication, and client-facing interfaces

Use when analyzing domain entities, value objects, aggregates, and business rules encoded in the model

Use when analyzing end-to-end tests including browser automation, API workflows, and full system testing

Use when analyzing frontend/UI layer including components, state management, routing, and API integration (optional - skip if no frontend exists)

Use when analyzing integration tests that verify component interactions, database access, and external service integration

Use when analyzing event-driven systems, message queues, async processing, and pub/sub patterns

Use when analyzing business logic, use cases, service orchestration, and data transformation including DTOs and mappers

Use when analyzing unit test coverage, patterns, and test code for isolated component testing

Use to update an existing Unwind analysis after code changes — re-analyzes only the affected layers instead of re-unwinding the whole codebase