flow-project-bootstrap

Orchestrate a two-stage project kickoff from discovery through build scaffold.

Updated May 12, 2026
One-click install
npx skills add https://github.com/YeomanYe/skills --skill flow-project-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow-project-bootstrap
Source: https://github.com/YeomanYe/skills/tree/main/flow-project-bootstrap
Command: npx skills add https://github.com/YeomanYe/skills --skill flow-project-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a two-stage project kickoff workflow that ensures design decisions and engineering scaffolding are locked in before implementation.

Core Features & Use Cases

  • Stage 1: Discovery & Direction to produce a comprehensive total design document including MVP scope, ASCII process flow, preview design plan, design system candidates, deployment strategy, and post- kickoff roadmap.
  • Stage 2: Build Scaffold to generate engineering norms, project branding, and a usable preview page with two-way linking to the design doc.
  • Use Case: When a team wants a full-package kickoff from requirements to kickoff including MVP scoping, design direction, and deployment plan.

Quick Start

Provide a complete two-stage kickoff plan by delivering Stage 1 total design document followed by Stage 2 engineering scaffold and artifacts after the user confirms key decisions.

Frequently Asked Questions about flow-project-bootstrap

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

FAQPage Schema
How do I coordinate a full project kickoff from discovery to scaffold?

A full project kickoff requires orchestrating a two-stage workflow: Stage 1 produces a total design document with MVP scope and ASCII process flow, while Stage 2 generates the engineering scaffold, branding, and preview page with dual linking back to the design doc.

What is included in a total design document for MVP project management?

A total design document for MVP project management includes MVP scope definition, an ASCII process flowchart, preview design plan, design system candidates, deployment strategy, and a post-kickoff roadmap to lock in decisions before implementation.

How do I generate engineering standards and a preview page for a greenfield project?

Generating engineering standards and a preview page for a greenfield project happens during the build scaffold stage, which outputs engineering norms, project branding like logo design, and a usable preview page with two-way linking to the design document.

Can I use this two-stage kickoff workflow for existing projects or is it only for greenfield initiatives?

This two-stage kickoff workflow applies specifically to greenfield projects and new initiatives seeking a full-package kickoff including MVP scoping, design direction, and deployment planning, rather than existing project modifications.

What's the best way to structure a project kickoff workflow with deployment planning and design direction?

The best way to structure a project kickoff with deployment planning is a two-stage approach: first produce a comprehensive total design document covering MVP and deployment strategy, then confirm key decisions before generating the engineering scaffold and artifacts.

Do I need to confirm key decisions before generating the engineering scaffold?

Yes, you need to confirm key decisions from the Stage 1 total design document before Stage 2 begins, ensuring the engineering scaffold, preview page, and logo design are generated based on locked-in MVP scope and deployment strategy.