Define MVP scope, core interactions, and tech stack into a Prep Brief.
npx skills add https://github.com/YeomanYe/skills --skill project-prep
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
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.
Provide an initial project prep brief for a new product by defining MVP, core interactions, and the chosen tech stack.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
silaslopes100Convert raw product ideation data into structured user personas and customer journey maps.
HareryTransform architecture into a development roadmap with WBS, resource, risk, and QA plans.
yezannnnnAnalyze architecture choices and document rationale in ADRs with Mermaid, PlantUML, or ASCII diagrams.
erclxSequence MVP feature requirements into a versioned Markdown roadmap table.
