bizanalysis

Analyze product idea business viability and generate a go/no-go decision for sprint planning.

11|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pillip/claude-dev-kit --skill bizanalysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bizanalysis
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/bizanalysis
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill bizanalysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Analyzes and critiques business viability to determine whether ideas should advance into PRDs or be revised.

Core Features & Use Cases

  • Structured evaluation: Systematically assesses market potential, risks, and alignment with sprint goals.
  • Context-aware guidance: Uses existing brainstorm notes and PRD draft state to tailor recommendations.
  • Go/No-Go decisioning: Produces actionable next steps and a recommended decision for /prd planning.

Quick Start

Summarize market viability and provide a go/no-go recommendation for the current brainstorm.

Frequently Asked Questions about bizanalysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate business viability before writing a PRD?

Validating business viability requires assessing market potential, competitive landscape, and sprint alignment to produce a go/no-go decision before PRD drafting. This ensures only feasible ideas advance, shaping PRD scope and prioritizing features based on structured risk assessment.

What is a go/no-go decision in sprint planning?

A go/no-go decision in sprint planning is an actionable recommendation determining whether a product idea should advance into a PRD. It surfaces market risks and mitigations to inform the sprint backlog, ensuring development resources target viable business bets.

Can I analyze competitive analysis and market research for product strategy without existing PRD drafts?

Analyzing competitive analysis and market research for product strategy works best with existing brainstorm notes. While PRD drafts provide additional context, the core evaluation relies on brainstorm outputs to systematically assess market potential and tailor risk mitigations.

How do I prioritize features and surface risks for sprint backlog preparation?

Prioritizing features and surfacing risks requires applying structured business analysis after brainstorming. This process critiques idea viability, generates risk mitigations, and outputs actionable recommendations that directly shape sprint backlog scope before PRD creation.

When should I not use business analysis for product idea evaluation?

Business analysis for product idea evaluation should be skipped if you lack brainstorm notes or sprint planning context. Without these inputs, the structured evaluation cannot tailor recommendations or effectively assess alignment with sprint goals.

Does the bizanalysis Skill require any dependencies to run?

The bizanalysis Skill requires no external dependencies to run. It operates independently using scripts to analyze brainstorm notes and PRD draft states, delivering go/no-go recommendations and risk mitigations for sprint planning.