Screenshot Feature Extractor

davila7/claude-code-templates/cli-tool/components/skills/development/screenshot-feature-extractor

by davila78da17d671b6fNo license32K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

AI-generated overview

Analyzes product UI screenshots to extract feature lists and produce development task checklists.

What it does
This skill orchestrates a multi-agent pipeline that reads product screenshots and analyzes them from UI, interaction, and business perspectives in parallel. A synthesizer then merges the results into a unified feature and task list, which a reviewer validates. The final output is a markdown task checklist written to a dated file under docs/plans, using the format defined in its reference document.
When to use it
Use it when extracting features from competitor product screenshots, turning UI designs into PRD or task lists, batch-analyzing multiple app screens, or conducting competitive analysis from visual references.
Requirements
Requires an agent environment with screenshot image files and the Task tool for launching sub-agents. It ships no scripts; it references a bundled output-format document and writes output to docs/plans/.

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 [blocked]
  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

Source and attribution

Source:davila7/claude-code-templatesincli-tool/components/skills/development/screenshot-feature-extractorat commit8da17d6

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal