home / skills / davila7 / claude-code-templates / screenshot-feature-extractor

This skill analyzes product screenshots to extract feature lists and generate development task checklists for PRDs and roadmaps.

npx playbooks add skill davila7/claude-code-templates --skill screenshot-feature-extractor

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
5.0 KB
---
name: screenshot-feature-extractor
description: "Analyze product screenshots to extract feature lists and generate development task checklists. Use when: (1) Analyzing competitor product screenshots for feature extraction, (2) Generating PRD/task lists from UI designs, (3) Batch analyzing multiple app screens, (4) Conducting competitive analysis from visual references."
---

# Screenshot Analyzer (Multi-Agent)

Extract product features from UI screenshots using a coordinated multi-agent analysis pipeline.

**Core principle**: Describe WHAT to build (features/interactions), NOT HOW (no tech stack).

## Multi-Agent Architecture

This skill orchestrates 5 specialized agents for comprehensive analysis:

```
                    ┌─────────────────┐
                    │   Coordinator   │
                    │   (this skill)  │
                    └────────┬────────┘
                             │
         ┌───────────────────┼───────────────────┐
         │                   │                   │
         ▼                   ▼                   ▼
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│  UI Analyzer    │ │  Interaction    │ │   Business      │
│  (parallel)     │ │   Analyzer      │ │    Analyzer     │
│                 │ │  (parallel)     │ │   (parallel)    │
└────────┬────────┘ └────────┬────────┘ └────────┬────────┘
         │                   │                   │
         └───────────────────┼───────────────────┘
                             ▼
                    ┌─────────────────┐
                    │   Synthesizer   │
                    │   (sequential)  │
                    └────────┬────────┘
                             │
                             ▼
                    ┌─────────────────┐
                    │    Reviewer     │
                    │   (sequential)  │
                    └─────────────────┘
```

## Process

### Phase 1: Screenshot Collection

Gather all screenshots to analyze:
1. Read the screenshot file(s) provided by the user
2. For each screenshot, note the file path and any context provided
3. If multiple screenshots, determine if they are from the same product

### Phase 2: Parallel Analysis

Launch THREE Task agents IN PARALLEL for each screenshot:

**Agent 1: screenshot-ui-analyzer**
```
Analyze this screenshot for UI components, layout structure, and design patterns.
Screenshot: [file path]
Return your analysis as JSON.
```

**Agent 2: screenshot-interaction-analyzer**
```
Analyze this screenshot for user interactions, navigation flows, and state transitions.
Screenshot: [file path]
Return your analysis as JSON.
```

**Agent 3: screenshot-business-analyzer**
```
Analyze this screenshot for business functions, data entities, and domain logic.
Screenshot: [file path]
Return your analysis as JSON.
```

**IMPORTANT**: Use the Task tool with THREE parallel calls in a single message to maximize efficiency.

### Phase 3: Synthesis

After all parallel analyses complete, launch the synthesizer agent:

**Agent 4: screenshot-synthesizer**
```
Synthesize these analysis results into a unified development task list.

UI Analysis:
[paste UI analyzer result]

Interaction Analysis:
[paste Interaction analyzer result]

Business Analysis:
[paste Business analyzer result]

Product Name: [product name]
Output file: docs/plans/YYYY-MM-DD-<product>-features.md
```

### Phase 4: Review

Launch the reviewer agent to validate the output:

**Agent 5: screenshot-reviewer**
```
Review this task list for completeness and quality.

Original screenshot(s): [file paths]
Task list: [synthesized output]

If issues found, provide corrections.
```

### Phase 5: Output

1. Write final task list to `docs/plans/YYYY-MM-DD-<product>-features.md`
2. Use format from [references/output-format.md](references/output-format.md)
3. Present summary to user

## Key Guidelines

- Use `- [ ]` checkbox format for all tasks
- Break features into small, executable subtasks
- Focus on user interactions, not implementation details
- For multiple screenshots: deduplicate features across all screens
- For competitive analysis: highlight unique features and gaps

## Benefits of Multi-Agent Approach

1. **Thoroughness** - Three specialized perspectives catch more details
2. **Speed** - Parallel analysis reduces total time
3. **Quality** - Synthesis + Review ensures coherent, complete output
4. **Specialization** - Each agent focuses on its domain expertise

Overview

This skill analyzes product screenshots to extract feature lists and generate executable development task checklists. It uses a coordinated multi-agent pipeline to produce concise, user-focused feature descriptions and - [ ] style task breakdowns suitable for PRDs and sprint planning. It emphasizes WHAT to build (features and interactions), not implementation details.

How this skill works

The skill runs three specialized analyzers in parallel (UI, interaction, and business) to capture visual design, user flows, and domain intent from each screenshot. A synthesizer merges those JSON analyses into a unified feature list and detailed checklist, then a reviewer validates completeness and quality. Final output is written as a dated feature plan and presented as a summarized task list.

When to use it

  • Extract features from competitor screenshots for competitive analysis
  • Generate PRD-style task lists from UI mockups or design screens
  • Batch-analyze many app screens to produce a consolidated feature backlog
  • Identify gaps and unique features across similar products for product strategy
  • Prepare development checklists from final visual designs before sprint planning

Best practices

  • Provide clear context and product name for each screenshot to improve synthesis accuracy
  • Upload high-resolution screenshots and include multiple states if available (e.g., modal open, item selected)
  • Group related screens and indicate which belong to the same product or flow to enable deduplication
  • Expect concise, user-facing feature descriptions; iterate with clarifying screenshots or notes if needed
  • Use the produced - [ ] task checklist directly in planning tools after review and assignment

Example use cases

  • Competitive feature audit: extract unique UI elements and business logic from competitor screenshots
  • PRD generation: convert UI designs into a prioritized task checklist for engineering
  • Batch processing: analyze an app’s screens to produce a single consolidated feature plan
  • Gap analysis: highlight missing or poorly supported flows compared to competitors
  • Sprint prep: break extracted features into small, testable subtasks for immediate planning

FAQ

What format does the skill output?

It writes a dated feature plan file and returns a summarized task list using - [ ] checkbox format so items can be moved directly into trackers.

How does parallel analysis speed things up?

Three specialized analyzers run in parallel (UI, interaction, business) to capture different perspectives simultaneously; a synthesizer then merges results for higher coverage and faster turnaround.