screenshot-feature-extractor
Verifiedby davila7 · Updated Apr 16, 2026
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.
See It In Action
Let me find the screenshots and understand the project structure first.
Found all 6 screenshots. Let me also check the references folder, then invoke the screenshot feature extractor skill.
Good — I have the output format template and all 6 screenshots. Now let me run the skill to analyze all screenshots in batch.
Let me read all 6 screenshots first.
All 6 screenshots loaded. The product is FocusCraft — a productivity app with AI focus sessions, smart scheduling, team sync, and a freemium/Pro paywall. Now launching the three parallel analysis agents.
All three analyses are back. Now let me synthesize them into a unified feature checklist, then review it.
Good synthesis. Now let me run the review agent against the original screenshots to validate completeness, then write the final output.
Review found a 7/10 with specific corrections needed. Let me incorporate all the fixes and write the final reviewed output.
Done. The reviewed feature checklist is at docs/plans/2026-04-11-focuscraft-features.md.
What was analyzed
All 6 FocusCraft screenshots were run through 3 parallel analysis agents (UI components, interaction flows, business model), then synthesized and reviewed against the originals.
What the review caught and I fixed
- Moved social proof ("Trusted by 50K+ teams") to the correct screen (Paywall, not Welcome)
- Added missing Welcome screen feature pills (AI-Powered Focus, Smart Scheduling, Team Sync)
- Added missing Signup fields (Full Name, ToS/Privacy link, back button)
- Added missing Profile Setup elements (avatar/photo upload, progress bar)
- Added "Priority support" as a Pro-gated feature
- Added specific CTA labels ("Go to Dashboard", "Start Free Trial -- Pro")
- Added feature tour mock UI details (task cards with priority/due-date labels, 25:00 timer)
Checklist breakdown
| Section | Tasks |
|---|---|
| Onboarding Flow | 42 items across 7 screens |
| Core Features | 22 items (Focus, Scheduling, Tasks, Team, Analytics) |
| Monetization | 15 items (plans, trial, gating, upsells) |
| User Engagement | 13 items (activation, virality, personalization, login) |
| Integrations | 5 items (Slack, Calendar, Jira) |
Ready for sprint prioritization with leadership.
Permissions
| Scope | Description |
|---|---|
| filesystem:read | |
| filesystem:write |
SKILL.md
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:
- Read the screenshot file(s) provided by the user
- For each screenshot, note the file path and any context provided
- 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
- Write final task list to
docs/plans/YYYY-MM-DD-<product>-features.md - Use format from references/output-format.md
- 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
- Thoroughness - Three specialized perspectives catch more details
- Speed - Parallel analysis reduces total time
- Quality - Synthesis + Review ensures coherent, complete output
- Specialization - Each agent focuses on its domain expertise
FAQ
What does screenshot-feature-extractor do?
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.
When should I use screenshot-feature-extractor?
Use it when you need a repeatable workflow that produces text report.
What does screenshot-feature-extractor output?
In the evaluated run it produced text report.
How do I install or invoke screenshot-feature-extractor?
npx skills add https://github.com/davila7/claude-code-templates --skill screenshot-feature-extractor
Which agents does screenshot-feature-extractor support?
Claude Code
What tools, channels, or permissions does screenshot-feature-extractor need?
It uses no extra tools; channels commonly include text; permissions include filesystem:read, filesystem:write.
Is screenshot-feature-extractor safe to install?
Static analysis marked this skill as medium risk; review side effects and permissions before enabling it.
How is screenshot-feature-extractor different from an MCP or plugin?
A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.
Does screenshot-feature-extractor outperform not using a skill?
About screenshot-feature-extractor
When to use screenshot-feature-extractor
When you have one or more product UI screenshots and need a feature list or implementation checklist. When converting visual designs or competitor app screens into PRD-style development tasks. When analyzing multiple screens to identify shared and unique product capabilities.
When screenshot-feature-extractor is not the right choice
When you need actual implementation code or technical architecture decisions rather than feature-level requirements. When there are no screenshots or visual references to analyze.
What it produces
Produces text report.
Install
npx skills add https://github.com/davila7/claude-code-templates --skill screenshot-feature-extractorInvoke: Ask Claude Code to use screenshot-feature-extractor for the task.