app-idea-workshop

Guide ideation through structured interviews and generate product documentation.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/CAPHTECH/claude-marketplace --skill app-idea-workshop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-idea-workshop
Source: https://github.com/CAPHTECH/claude-marketplace/tree/main/caphtech-plugin/skills/app-idea-workshop
Command: npx skills add https://github.com/CAPHTECH/claude-marketplace --skill app-idea-workshop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

Guides ideation through structured interviews and generates production-ready docs.

Core Features & Use Cases

  • Vision exploration and collaborative deep-dive
  • Phase-based functional spec generation
  • Output: product docs, user stories, roadmaps, and non-functional requirements

Quick Start

Start with a rough idea and use this skill to produce a complete development doc set.

Frequently Asked Questions about app-idea-workshop

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

FAQPage Schema
How do I turn an app idea into actionable documentation?

Structured ideation generates actionable documentation by guiding you through phase-aligned interviews—from vision exploration through feature definition and validation—producing product specs, user stories, roadmaps, and requirements in a predefined template structure ready for development.

What's the best way to document user stories and feature requirements during ideation?

Co-creative deep-dives with phase-based prompts capture functional and technical requirements systematically. The workflow produces user stories, feature specs, and non-functional requirements as structured output that satisfies both product and engineering needs.

Can I generate a product roadmap and documentation package from a rough app concept?

Yes. Starting with a rough idea, this approach conducts collaborative interviews across ideation to MVP phases, then generates a complete documentation package including roadmaps, user stories, functional specs, and technical requirements in a fixed directory structure.

How do I validate app features before writing technical specs?

Phase-aligned validation occurs during co-creative exploration and deep-dives, where collaborative questioning surfaces feature assumptions and technical constraints. Validated outputs feed directly into structured documentation.

What documentation does this produce for web and mobile app development?

Output includes product documentation, user stories, roadmaps, functional specs, and non-functional requirements—all organized in predefined templates with fixed directory structure suited for both web and mobile app development workflows.