wds-0-project-setup

Determine WDS workflow paths and route projects to the correct phase.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill wds-0-project-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wds-0-project-setup
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/wds-0-project-setup
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill wds-0-project-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from starting in the wrong workflow by quickly determining whether a project is greenfield or brownfield, how complex it is, and which WDS phase should come next.

Core Features & Use Cases

  • Project onboarding: Introduces WDS, clarifies project type, and checks whether stakeholder alignment or signoff is needed.
  • Configuration capture: Collects project name, product complexity, tech stack, component library, brief depth, and working relationship context.
  • Workflow routing: Directs users to the correct next step, including Phase 1, Phase 8, or the alignment and signoff workflow.
  • Structure generation: Guides creation of the project folder structure and the initial WDS project outline.
  • Use Case: A team joining an existing Next.js repository can use this Skill to confirm they are in brownfield mode, record setup decisions, and avoid accidentally launching into the wrong design phase.

Quick Start

Use the WDS project setup skill to inspect the repository, identify the project type, capture the required configuration, and route the work to the correct next phase.

Frequently Asked Questions about wds-0-project-setup

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

FAQPage Schema
How do I route a new project to the correct workflow phase during onboarding?

Project onboarding routing requires determining whether your project is greenfield or brownfield, assessing complexity, and capturing configuration choices to direct the work to the proper phase. This workflow routing process prevents teams from starting in the wrong design stage.

What is the difference between greenfield and brownfield project setup?

Greenfield project setup starts from scratch with no existing codebase, while brownfield setup involves joining an existing repository like a Next.js project. Detecting the project type dictates configuration capture and routes work to the correct workflow phase.

How do I set up an existing Next.js repository for brownfield project onboarding?

Brownfield project onboarding involves inspecting the existing repository, confirming the project type, recording setup decisions like tech stack and component library, and routing to the correct next phase to avoid launching into the wrong design step.

What configuration details do I need to capture for workflow routing?

Workflow routing requires capturing the project name, product complexity, tech stack, component library, brief depth, and working relationship context. These configuration choices determine whether the project proceeds to Phase 1, Phase 8, or the alignment and signoff workflow.

Does project setup work for teams that need stakeholder alignment before routing?

Yes, project setup checks whether stakeholder alignment or signoff is needed during onboarding. If required, the workflow routes the team to the alignment and signoff workflow before advancing to any subsequent design phase.

When should I not skip the project setup phase before starting design work?

You should not skip setup when onboarding a new or existing project, as routing to the wrong workflow phase occurs without confirmed project type and configuration choices. Structure generation and initial outline creation depend on completing Phase 0 setup instructions.