feature-analyzer
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing…
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
$ npx -y skills add notedit/happy-skills --skill screenshot-analyzer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/screenshot-analyzerContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: screenshot-analyzer 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."
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).
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) │
└─────────────────┘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
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.
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
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.
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
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
Turn ideas into fully formed designs and specs through natural collaborative dialogue. Use when planning new features, designing…
Guided feature development with codebase understanding and architecture focus. Use for implementing features systematically:…
Execute implementation tasks from design documents using markdown checkboxes. Use when (1) implementing features from…
AI-Native Issue-Driven development workflow. From GitHub Issue to merged PR: parse issue, explore codebase, design technical…
Generate article cover images with 5 dimensions (type, palette, rendering, text, mood). Supports cinematic (2.35:1), widescreen…
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing…