scaffold-mvp

Initializes a product-grade MVP repository with structure, compliance wiring, and deploy stubs.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill scaffold-mvp-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scaffold-mvp
Source: https://github.com/jokerman89/lintel/tree/main/skills/scaffold-mvp
Command: npx skills add https://github.com/jokerman89/lintel --skill scaffold-mvp-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a new product MVP repository involves repetitive decisions about directory structure, compliance artifacts, eval suites, and deploy configuration. This Skill automates that greenfield setup so teams start with a consistent, reviewable foundation instead of ad-hoc scaffolding. ## Core Features & Use Cases - Full repo scaffolding: Creates source, test, docs, CI workflow, and changelog directories with starter files, plus a CLAUDE.md with frozen zones protecting finalized compliance and eval artifacts. - Pack-driven compliance and voice wiring: Pre-wires the active pack's compliance gates as DRAFT stubs and a CI compliance-check workflow, with no-op behavior when only the default pack is active. - AI eval skeleton: When --has-ai is enabled, seeds an eval suite with golden and adversarial fixture directories and methodology guidance. - Use Case: A team spinning a validated prototype into a customer-facing product runs the skill with a name, target users, and deploy targets, and receives a git-initialized repo ready for design docs, compliance review, and first feature work. ## Quick Start Ask the agent to scaffold a new MVP named billing-portal for mid-market SMB CFOs with AI disabled and a staging deploy target.

Frequently Asked Questions about scaffold-mvp

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

FAQPage Schema
How do I scaffold a new MVP repository with compliance wiring?▼

Run the skill with a required --name slug and --target-users description, plus optional --stack, --has-ai, and --deploy flags. It creates the full directory structure, CLAUDE.md, compliance stubs from the active pack, and a git first commit.

What is the difference between scaffold-mvp and scaffold-internal-tool?▼

scaffold-mvp targets products shipping to real users and includes compliance gates, voice wiring, eval suites, and deploy stubs. scaffold-internal-tool is a lighter variant for internal utilities without a customer-facing surface.

Can I use scaffold-mvp on an existing repository?▼

No, this skill is greenfield-only. Adding its structure to an existing repo is treated as a refactor, and if the target path already exists the skill asks whether to merge or pick a new path.

What happens when the active pack is _default?▼

With the default pack, no compliance or voice gates are wired. The compliance-check CI workflow becomes a no-op, and no pack-specific DRAFT stubs are created, leaving a lighter compliance surface.

Why does scaffold-mvp require the --target-users argument?▼

The skill requires target users because every product has an audience, and declaring it shapes voice gating and compliance scope. An empty value is rejected rather than defaulted.