using-unwind

Document reverse-engineering workflows and layer mappings with Unwind.

9|Updated Jan 15, 2026

Search Tags:#workflow #architecture #documentation #codebase #reverse-engineering #layer-analysis #unwind

Ready to run

npx skills add https://github.com/cliftonc/unwind --skill using-unwind

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: using-unwind
Source: https://github.com/cliftonc/unwind/tree/main/skills/using-unwind
Command: npx skills add https://github.com/cliftonc/unwind --skill using-unwind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Unwind skills framework standardizes how teams approach reverse-engineering tasks by providing a structured, repeatable workflow that captures architecture, layer mappings, and repository insights for AI-driven codebase understanding.

Core Features & Use Cases

Guides users through a disciplined discovery and documentation process for codebases.
Maps layers (database, domain-model, service, api, messaging, frontend) and outputs consistent documentation artifacts.
Enables reproducible rebuild planning by producing REBUILD-PLAN.md and architecture references.

Quick Start

Run unwind:start to begin capturing architecture and layer information for the target codebase.

Frequently Asked Questions about using-unwind

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I document a codebase for reverse-engineering?▼

Codebase documentation for reverse-engineering uses a structured workflow to map database, domain model, service, and API layers. It generates consistent artifacts like architecture.md to enable AI-driven codebase analysis and reproducible rebuild planning.

What is layer analysis in codebase architecture?▼

Layer analysis maps structural levels like database, domain model, service, API, and optional messaging or frontend tiers. It enforces structured documentation outputs to provide comprehensive architectural insights for AI-driven codebase understanding.

How do I create a reproducible rebuild plan for an existing codebase?▼

Creating a reproducible rebuild plan involves running a reverse-engineering workflow that outputs a REBUILD-PLAN.md file alongside architecture references. This standardizes repository insights and layer mappings for consistent codebase reconstruction.

Can I map messaging and frontend layers in addition to core services?▼

Yes, you can map messaging and frontend layers alongside core services. The workflow supports optional layer analysis including messaging, frontend, and tests alongside database, domain model, service, and API mappings for comprehensive documentation.

What's the best way to standardize architecture documentation across multiple repositories?▼

Standardizing architecture documentation requires a repeatable discovery workflow enforcing structured outputs like docs/unwind/* and architecture.md. This ensures consistent layer mappings and repository insights across teams for AI-driven analysis.