project-prep

Define MVP scope, core interactions, and tech stack into a Prep Brief.

Updated May 12, 2026

Search Tags:#planning #MVP #preview #tech-stack #prep-brief #project-prep #core-interactions

Ready to run

npx skills add https://github.com/YeomanYe/skills --skill project-prep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-prep
Source: https://github.com/YeomanYe/skills/tree/main/project-prep
Command: npx skills add https://github.com/YeomanYe/skills --skill project-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams converge vague inception ideas into a concrete project prep brief, clearly specifying MVP scope, core interactions, main tech stack, and a preview decision before implementation.

Core Features & Use Cases

Define MVP scope with target users, primary flows, and success criteria, ensuring a clear path from entry to value delivery.
Determine the main interaction design and tech choices to guide early architecture and roadmap decisions.
Decide whether a preview is needed, and produce a structured Prep Brief that channels work to downstream teams with Open Decisions.

Quick Start

Provide an initial project prep brief for a new product by defining MVP, core interactions, and the chosen tech stack.

Frequently Asked Questions about project-prep

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

FAQPage Schema

How do I define MVP scope and core interactions before project kickoff?▼

Core interactions for an MVP are the primary user flows that deliver value directly. Defining them upfront involves mapping target users to success criteria, which aligns interaction design and tech choices to guide early architecture decisions before implementation begins.

What is a project prep brief and when do I need one for a new software product?▼

A prep brief is a structured document specifying MVP scope, core interactions, tech stack, and preview decisions. You need one during pre-project planning for new software products or extensions where upfront clarity is required to channel work to downstream teams.

How do I decide whether a preview is needed for my MVP?▼

To decide whether an MVP preview is needed, evaluate your project prep brief against your target users and success criteria. This evaluation produces a recommended preview decision that guides downstream work and highlights any open decisions for the team.

What is the best way to align tech stack choices with MVP goals upfront?▼

The best way to align tech stack choices with MVP goals is to determine main interaction designs and tech choices concurrently during pre-project planning. This approach ensures early architecture decisions support the primary flows and success criteria defined in your prep brief.

Can I use this pre-project planning approach for existing product extensions?▼

Yes, this pre-project planning approach applies to new software products and existing product extensions. It captures MVP scope, core interactions, and tech stack upfront, producing a structured Prep Brief that guides downstream work for both scenarios.