gsd-new-project

Initialize new projects by generating PROJECT, REQUIREMENTS, ROADMAP, and STATE documents.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-new-project-electroheadfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-project
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-new-project
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-new-project-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you start a new project with a clear process for gathering context, defining requirements, and organizing the work into an actionable roadmap.

Core Features & Use Cases

  • Project Initialization: Creates the core planning artifacts needed to begin a project cleanly.
  • Context Gathering: Guides the user through questions and research so the project starts with the right assumptions and constraints.
  • Planning Workflow: Produces project, requirements, roadmap, and state files that support structured execution.
  • Use Case: Use this Skill when you need to turn a rough idea into a well-scoped project plan before implementation begins.

Quick Start

Use the gsd-new-project skill to initialize a new project and generate the planning artifacts.

Frequently Asked Questions about gsd-new-project

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

FAQPage Schema
How do I initialize a software project with structured requirements and a roadmap?

To initialize a software project, this Skill gathers context and requirements through interactive questioning, then generates structured PROJECT, REQUIREMENTS, ROADMAP, and STATE artifacts for a repeatable setup flow.

What is the best way to turn a rough software idea into an actionable project plan?

The best way to turn a rough idea into an actionable project plan is using a planning workflow that applies optional research and context gathering to produce a phased execution roadmap before implementation begins.

How do I gather context and constraints before starting early-stage software initiatives?

You gather context and constraints by answering interactive questions that guide you through project assumptions, ensuring your early-stage software initiatives start with the right foundational inputs.

Does project initialization require interactive questioning support to work?

Yes, project initialization requires interactive questioning support to accurately gather context and requirements, enabling workflow-aware file generation for your planning artifacts.

What planning documents are needed to cleanly begin a software project?

The planning documents needed to cleanly begin a software project are PROJECT, REQUIREMENTS, ROADMAP, and STATE files, which collectively support structured execution and organization.

When should I not use an automated context gathering workflow for project initialization?

You should not use an automated context gathering workflow for project initialization if your software project is past the early-stage phase or already has defined requirements and a phased execution roadmap.