detail-exploration

What problem does it solve?

Converts exploration run output into structured, reviewable engineering tickets or product user stories so teams do not have to manually translate reports and screenshots into implementable work items. It preserves traceability to the exploration report, ensures acceptance criteria and verification steps are included, and supports resumable workflows to avoid duplicated effort.

Core Features & Use Cases

• Read Explore App Settings from .claude/skill-config.md and locate the exploration output directory.
• Parse the progress log and plan (ticket or story mode), then flesh out selected items into formatted markdown tickets or user stories with context, API/data notes, design tokens, and references.
• Support selective detailing by ID, ranges, or "all", resume interrupted work, present a post-generation review summary, and track revision counts in PROGRESS.md.
• Use case: After crawling an app with /explore-app, run this Skill to produce engineering-ready tickets for prioritized screens, complete with screenshots, selectors, acceptance criteria, and verification instructions.

Quick Start

Detail the plan items EX-01 through EX-05 into tickets and save them into the exploration output directory.