Sw Idea Analyzer

SW Idea Analyzer

Overview

Analyzes any software or product idea with a structured framework: feasibility, target audience, core features, technical complexity, risks, and MVP scope. Pure planning and analysis – no code generation, no external calls.

Language detection: Read the user's input language and respond entirely in that language. If the language cannot be determined, default to German.

When to Use

• User describes an app, tool, platform, or startup idea
• User wants to know if an idea is worth pursuing
• User needs help defining MVP scope before development starts
• User wants risks and challenges surfaced early
• User asks "is this a good idea?" or "what would I need to build X?"

When NOT to Use

• User already has a spec and wants user stories → use /sw-user-story-creator
• User wants to pick a tech stack → use /sw-tech-stack-planner
• User wants diagrams of their architecture → use /sw-diagram-creator

Analysis Framework

Run all eight sections in order. Adjust depth based on detail in user's input.

1. Idea Summary

One sentence restatement of the core idea in plain language. No jargon.

2. Target Audience

3. Problem & Solution Fit

• Core problem: What frustration or inefficiency does this solve?
• Solution approach: How does the idea address it?
• Differentiation: What makes this different from existing tools?

4. Core Features (MVP)

Top 5 must-have features for a usable first version:

Features explicitly out of MVP scope: list at least 3 things to defer.

5. Technical Complexity

Rate overall complexity: 🟢 Simple / 🟡 Medium / 🔴 Complex

Assess each dimension:

6. Market & Competition

List 2–3 existing alternatives and explain the differentiation angle:

7. Top Risks

8. Next Steps

3–5 concrete, immediately actionable steps the user can take after this analysis. Be specific, not generic.

Output Rules

• Never print the analysis to the chat. All output goes to files only.
• Do not show tables, sections, or any analysis content in the chat.
• The only chat output allowed is the final confirmation line.
• Always use the user's input language in the file content.
• Use tables for structured data (features, risks, competition) inside the file.
• Never generate code.
• Never make API calls or use external tools.

File Output

After completing the full analysis, write everything to requirements/vision.md. Print nothing to the chat except the confirmation.

Steps:

1. If requirements/ does not exist, create it first: mkdir -p requirements
2. Write the complete structured analysis (all 8 sections, clean Markdown) to requirements/vision.md
3. Print only these lines to the chat:

✅ Analysis complete. Please review: requirements/vision.md

▶ Next steps:

• Run /sw-user-story-creator to turn the vision into user stories with acceptance criteria
• Run /sw-diagram-creator to visualize the architecture

requirements/vision.md structure:

# Vision: <Idea Title>

## Idea Summary
...

## Target Audience
| Segment | Description | Primary Pain Point |
...

## Problem & Solution Fit
...

## Core Features (MVP)
| # | Feature | Why It's Core |
...

## Technical Complexity
...

## Market & Competition
...

## Top Risks
...

## Next Steps
...

## Suggested Next Skill
...

Next Skill

At the end of every analysis, suggest the most logical next step:

Suggested next skill:

• Got clear features? → Run /sw-user-story-creator to turn them into user stories with acceptance criteria
• Need diagrams? → Run /sw-diagram-creator to visualize the architecture or data model
• Ready to plan the tech stack? → Run /sw-tech-stack-planner to pick the right framework and database