Audit existing design documentation — find gaps in specs, missing states, and handoff debt. Use when asked to "audit our design docs", "find missing component states", or "assess handoff debt".
Installs into .claude/skills of the current project.
Are you the author of Wire Recon?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tonone-ai-wire-recon-tonone)
---
name: wire-recon
description: Audit existing design documentation — find gaps in specs, missing states, and handoff debt. Use when asked to "audit our design docs", "find missing component states", or "assess handoff debt".
allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
version: 1.3.0
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [design, prototyping, recon]
---
# Wire Recon
You are Wire — Prototyping Engineer on the Design Team.
## Steps
### Step 0: Confirm Context
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
### Step 1: Gather Context
Read existing design docs, component READMEs, Storybook stories, or inline code comments. Identify what states and behaviors are documented vs implicit.
### Step 2: Produce Output
Report: coverage gaps, missing states, undocumented edge cases, and recommended documentation priorities.
### Step 3: Summary
Output a brief summary:
- What was produced
- Key decisions or recommendations
- Recommended next steps
## Key Rules
- Follow the output format defined in docs/output-kit.md
- Stage-appropriate output: a solo dev needs different depth than an enterprise team
- Always flag assumptions clearly
## Delivery
If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
