kta-idea-pipeline

Guide Android indie developers through four ideation phases to produce a Markdown idea brief.

4|Updated May 7, 2026
One-click install
npx skills add https://github.com/dantech0xff/dreams --skill kta-idea-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kta-idea-pipeline
Source: https://github.com/dantech0xff/dreams/tree/main/.agents/skills/kta-idea-pipeline
Command: npx skills add https://github.com/dantech0xff/dreams --skill kta-idea-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps indie Android developers rapidly turn vague app ideas into a concrete, testable plan by guiding them through discovery, generation, scope refinement, and brief production.

Core Features & Use Cases

  • Phase-guided ideation: four phases (discover, generate, refine, brief) that structure creative work and decision making.
  • Dual idea generation: Phase 1 outputs exactly two candidate ideas with structured problem, target user, core value, MVP scope, differentiation, and killer feature.
  • Scoped refinement: Phase 2 enforces risk/reward/tradeoffs and explicit scope decisions (surface, connectivity, sharing, accounts, MVP vs v2).
  • Mandatory brief output: Phase 3 emits a ready-to-use plan at plans/{slug}/idea-brief.md with 5–8 feature seeds for downstream pipelines.
  • Handoff-ready: Phase 4 surfaces a handoff prompt to trigger the PRD pipeline.

Quick Start

Describe your app idea or select a discovery seed to generate two candidate ideas and proceed through the four phases to complete an idea brief.

Frequently Asked Questions about kta-idea-pipeline

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

FAQPage Schema
How do I generate app ideas for an indie Android project?

To generate app ideas for an Android project, this pipeline automates end-to-end ideation through four phases—discovery, generation, scope refinement, and brief production—yielding a ready-to-use Markdown idea-brief.

What's the best way to define MVP scope and feature tradeoffs for an Android app?

Defining MVP scope for an Android app requires evaluating risk, reward, and tradeoffs; this pipeline's refinement phase enforces explicit scope decisions across surface, connectivity, sharing, and accounts to finalize the MVP.

Can I use this idea generation pipeline if I don't have an app idea yet?

Yes, you can use this idea generation pipeline without an initial app idea by selecting a discovery seed, which triggers the process to produce two structured candidate ideas for subsequent scope refinement.

How do I convert a vague app idea into a structured feature brief?

Converting a vague app idea into a structured brief happens by running it through a four-phase pipeline that outputs a ready-to-use Markdown file at plans/{slug}/idea-brief.md containing 5–8 feature seeds.

Does the idea generation pipeline output a brief for downstream PRD creation?

Yes, the idea generation pipeline outputs a brief for downstream PRD creation by finalizing a Markdown idea-brief and surfacing a mandatory handoff prompt in Phase 4 to trigger the PRD pipeline.