Skip to content
Development
Skill

/idea-validator

Orchestrates business idea validation via parallel sub-agents: Lean Canvas, JTBD, market/competitive/feasibility research, SWOT/PESTLE, and a weighted scorecard with verdict. Triggers on: "validate this idea", "evaluate my startup idea", "is this idea worth pursuing", "score

From plugin
armory
33998 skills2 agents1 command

Claude Code

$ npx -y skills add Mathews-Tom/armory --skill idea-validator --agent claude-code

SKILL.md

idea-validator.SKILL.md
name: idea-validator
description: 'Orchestrates business idea validation via parallel sub-agents: Lean Canvas, JTBD, market/competitive/feasibility research, SWOT/PESTLE, and a weighted scorecard with verdict. Triggers on: "validate this idea", "evaluate my startup idea", "is this idea worth pursuing", "score this business idea", "validate my pitch".'
metadata:
  version: 1.0.1
  complements: [market-analyzer, competitive-analyzer, feasibility-assessor]
  category: review
  tags: [idea-validation, lean-canvas, jtbd, swot]
  difficulty: advanced
  phase: define

Business Idea Validator

Purpose

Perform rigorous, multi-dimensional validation of business ideas by orchestrating parallel research and synthesizing findings into a scored, actionable report. The goal is honest assessment — surfacing what holds up under scrutiny and what does not — rather than cheerleading or reflexive dismissal.

Phase 1: Input Intake & Classification

Classify the input:

| Input Type | Indicators | Adaptation | | ---------------- | ------------------------------------------- | ------------------------------------------- | | Elevator pitch | 1-3 sentences, informal | Extract hypothesis, ask for missing details | | Business plan | Structured, multiple sections | Validate claims against research | | Feature proposal | Technical focus, existing product context | Narrow scope to feature viability | | Repo/codebase | File paths, code references | Technical feasibility + market fit | | Pivot assessment | "Should we pivot to...", comparison context | Compare current vs proposed direction |

Extract core elements from the input:

  • **Problem statement** — what pain point exists
  • **Proposed solution** — how it addresses the pain
  • **Target customer** — who experiences this problem
  • **Value proposition** — why this solution over alternatives
  • **Revenue model** — how it generates money

If any core element is missing or ambiguous, ask clarifying questions. Cap at 5 questions. Do not proceed with fabricated assumptions for missing elements — get real answers.

Phase 2: Lean Canvas Construction

Build a complete Lean Canvas using `references/lean-canvas.md` as the framework guide.

Populate all 9 boxes:

1. **Problem** — top 3 problems the customer faces 2. **Customer Segments** — target market + early adopter profile 3. **Unique Value Proposition** — single clear compelling message 4. **Solution** — top 3 features addressing the top 3 problems 5. **Channels** — path to reaching customers 6. **Revenue Streams** — pricing model and revenue mechanics 7. **Cost Structure** — fixed and variable costs 8. **Key Metrics** — what to measure for progress 9. **Unfair Advantage** — what cannot be easily copied or bought

For each box:

  • Assess completeness and specificity
  • Flag vague entries ("everyone" as a segment, "best product" as UVP)
  • Check cross-box coherence (solution must address stated problems, channels must reach stated segments)

Phase 3: Jobs-to-be-Done Analysis

Apply the JTBD framework from `references/jtbd-framework.md`:

  • **Functional job** — what is the customer trying to accomplish?
  • **Emotional job** — how do they want to feel?
  • **Social job** — how do they want to be perceived?
  • **Current solutions** — what do they use today? (hiring/firing decisions)
  • **Switching triggers** — what would cause adoption of a new solution?

Assess whether the proposed solution addresses the core job better than current alternatives. Identify the four forces of progress: push of current situation, pull of new solution, anxiety of change, habit of status quo.

Phase 4: Parallel Research Delegation

Use the Agent tool to spawn three research agents in parallel. Each agent receives a focused research brief derived from the idea context established in Phases 1-3. These agents perform the same analysis covered by the complementary skills (`market-analyzer`, `competitive-analyzer`, `feasibility-assessor`) — when those skills are installed, their reference frameworks inform the analysis depth; when running standalone, the agents use the inline briefs below.

Agent 1 — Market Research

Prompt the agent:

> Analyze the market opportunity for [idea summary with target customer and problem context]. Research TAM/SAM/SOM estimates, market growth trends, customer segment sizing, and timing signals. Use WebSearch to find industry reports, market data, analyst projections, and trend indicators. Produce a structured market analysis with quantified estimates and cited sources. Include: market size estimates with methodology, growth rate and trajectory, key market drivers, timing assessment (too early, right time, too late), and customer willingness to pay signals.

Agent 2 — Competitive Analysis

Prompt the agent:

> Analyze the competitive landscape for [idea summary with solution and value proposition context]. Discover direct competitors (same solution, same customer), indirect competitors (different solution, same job-to-be-done), and potential competitors (adjacent players who could enter). Compare features, pricing, and positioning across competitors. Assess Porter's Five Forces for this industry. Identify moats and defensibility factors. Use WebSearch for competitor data from Product Hunt, G2, Capterra, Crunchbase, and company sites. Produce a structured competitive analysis with competitor matrix, force scores, and positioning assessment.

Agent 3 — Feasibility Assessment

Prompt the agent:

> Assess the financial and technical feasibility of [idea summary with solution details and revenue model]. Calculate unit economics using industry benchmarks: customer acquisition cost (CAC), lifetime value (LTV), LTV:CAC ratio, gross margins, payback period. Evaluate technical complexity: architecture requirements, key technical risks, bui

Read more
@mathews-tom
Ships witharmory

Curated, production-grade skills, agents, hooks, rules, commands, utilities, and presets for AI coding agents. No magic, no demos — battle-tested workflows built for developers who use AI seriously.

33998 skills2 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
339
Star history of Mathews-Tom/armory on GitHub, a chart by star-history.com

Other skills on armory.

doc-condenser

doc-condenser

**DEPRECATED** — Modern Claude models condense and summarize technical documentation natively with comparable quality. The output…

@mathews-tom@mathews-tomInstall Skill
opus-4-7-migration

opus-4-7-migration

DEPRECATED: The Opus 4.7 migration scanner is retired from the active skill catalog. Retained for archival reference only; not…

@mathews-tom@mathews-tomInstall Skill
regex-builder

regex-builder

**DEPRECATED** — Modern Claude models produce accurate, well-explained regex patterns with edge-case test suites natively,…

@mathews-tom@mathews-tomInstall Skill
sequential-thinking

sequential-thinking

**DEPRECATED** — Opus 4.7 uses adaptive thinking (optional at each step) and Sonnet 4.6 handles structured chain-of-thought…

@mathews-tom@mathews-tomInstall Skill
adr-writer

adr-writer

Generates Architecture Decision Records capturing context, rationale, alternatives, and consequences in numbered status-tracked…

@mathews-tom@mathews-tomInstall Skill
agent-builder

agent-builder

Build AI agents and automate Claude Code programmatically via the Claude Agent SDK and headless CLI mode. Covers Python SDK,…

@mathews-tom@mathews-tomInstall Skill

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react5d252k
@facebook@facebookInstall Skill

Questions about idea-validator.

Which coding agents can use idea-validator?
idea-validator installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.