new-app

Capture SaaS business logic via guided interview into a BUSINESS_LOGIC.md file.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/marcoapereirav-arch/nvision-saas-factory --skill new-app-marcoapereirav-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-app
Source: https://github.com/marcoapereirav-arch/nvision-saas-factory/tree/main/saas-factory/.claude/skills/new-app
Command: npx skills add https://github.com/marcoapereirav-arch/nvision-saas-factory --skill new-app-marcoapereirav-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This interview-driven process captures the core business logic of a SaaS idea by guiding the user to articulate pain points, value proposition, and required features, then generates a BUSINESS_LOGIC.md.

Core Features & Use Cases

  • Guided business-interview flow to extract problem, cost, and desired outcomes for a new app or SaaS project.
  • Generates a BUSINESS_LOGIC.md that codifies requirements, success metrics, and data flows.
  • Activates when the user expresses intent like "I want to create an app" or similar.

Quick Start

Describe your SaaS idea and let the system produce BUSINESS_LOGIC.md.

Frequently Asked Questions about new-app

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

FAQPage Schema
How do I extract business logic for a new SaaS app from an initial idea?

To extract business logic for a new SaaS app, you describe your initial idea and a guided interview captures pain points, user roles, data flows, and success metrics. This structured interview process outputs a BUSINESS_LOGIC.md file codifying your requirements.

What is a guided business interview for product discovery?

A guided business interview for product discovery is a structured question flow that helps you articulate the problem, cost, and desired outcomes of a new app. It enforces a process to capture core requirements and generate executable business logic documentation.

How do I define requirements and success metrics for a SaaS startup from scratch?

You define requirements and success metrics for a SaaS startup by walking through an interview that captures data inputs, outputs, and user roles. The session translates your early-stage product discovery notes into a structured BUSINESS_LOGIC.md file.

Can I generate a business logic document without prior technical specifications?

Yes, you can generate a business logic document without prior technical specifications by articulating your SaaS idea during a guided interview. The process extracts your pain points and value proposition to output the BUSINESS_LOGIC.md automatically.

What is the best way to document pain points and data flows for early-stage software requirements?

The best way to document pain points and data flows for early-stage software requirements is using a structured interview flow. It systematically captures user roles and desired outcomes, producing a BUSINESS_LOGIC.md suitable for agent execution.

When do I need a structured interview to define a product from scratch?

You need a structured interview to define a product from scratch when you have an initial SaaS idea but lack codified requirements. It enforces the extraction of pain points, costs, and success metrics required to build executable business logic.