review-million-dollar-app

Aggregate evidence and feedback for structured human review of app ideas.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aiguy611/cc-tools --skill review-million-dollar-app
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-million-dollar-app
Source: https://github.com/aiguy611/cc-tools/tree/main/.github/skills/review-million-dollar-app
Command: npx skills add https://github.com/aiguy611/cc-tools --skill review-million-dollar-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Interactive human review gates ensure evidence-based decisions for app ideas and verified apps, enabling consistent feedback and controlled automation.

Core Features & Use Cases

  • Evidence presentation: Show sources, tests, and demos to inform decisions.
  • Decision workflow: Collect APPROVE/DENY responses with cumulative feedback and status updates.
  • Auto-deny support: Accelerate early iterations by automatically denying, with human review later as needed.

Quick Start

Provide a slug to review, then choose whether to enable auto-deny or require human decision and start the process.

Frequently Asked Questions about review-million-dollar-app

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

FAQPage Schema
How do I set up a human review workflow for pending app ideas?

To set up a human review workflow, provide a slug for the app idea in pending_review status, then choose to enable auto-deny or require manual decision to start aggregating evidence and feedback.

What is auto-deny and when should I use it for app idea tracking?

Auto-deny is a safeguard that automatically denies initial app idea iterations to accelerate early workflow stages, deferring structured human review and manual decision-making to later phases as needed.

How does the review process present evidence to inform manual decisions?

The review process presents evidence by aggregating sources, tests, and demos to inform manual APPROVE or DENY decisions, while collecting cumulative feedback and updating tracking statuses.

Do I need a SKILL.md file to run the human review and tracking process?

Yes, the human review and tracking process requires a SKILL.md file at the root directory containing a name and description, alongside optional scripts, references, or assets to function properly.

Can I write cumulative feedback directly to planning docs during the review?

Yes, the review workflow outputs status updates and writes cumulative feedback directly to both tracking and planning docs after you collect an APPROVE or DENY response for the app idea.

What are the limitations of using auto-deny for initial iterations?

The limitation of using auto-deny for initial iterations is that it bypasses structured human review and evidence evaluation, meaning early app ideas are rejected without manual feedback or source verification.