gsd-new-project

Initialize projects by generating structured planning artifacts and phased roadmaps.

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-new-project-gesmith0606
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-project
Source: https://github.com/gesmith0606/nfl_data_engineering/tree/main/.claude/skills/gsd-new-project
Command: npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-new-project-gesmith0606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill consolidates the messy, early-stage project setup process by guiding discovery questions, optionally gathering domain research, and producing a single, versioned set of planning artifacts so teams avoid unclear goals and scattered notes.

Core Features & Use Cases

  • Guided Questioning: Interactive prompts capture project context, goals, stakeholders, constraints, and acceptance criteria.
  • Research Integration: Optionally collect and organize domain research into .planning/research/ for evidence-backed scoping.
  • Artifact Generation: Produces .planning/PROJECT.md, .planning/config.json, .planning/REQUIREMENTS.md, .planning/ROADMAP.md, and .planning/STATE.md to establish a single source of truth.
  • Workflow Preservation: Maintains validation gates, approvals, commits, and routing; supports an --auto flag to run research → requirements → roadmap without further interaction.
  • Use Case: Product managers or founders initiating a new feature or startup can produce scoped requirements and a phase-based roadmap along with research notes and configuration.

Quick Start

Initialize a new project by invoking the new-project workflow with an idea document reference and the --auto flag to produce PROJECT.md, requirements, and a phase roadmap.

Frequently Asked Questions about gsd-new-project

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

FAQPage Schema
How do I generate a project roadmap and requirements from initial discovery notes?

To generate a project roadmap and requirements, this Skill guides interactive discovery questioning, optionally gathers domain research, and outputs structured planning artifacts including ROADMAP.md and REQUIREMENTS.md. It consolidates scattered early-stage notes into a single versioned source of truth for engineering and product teams.

What is the best way to automate project initialization for a new startup feature?

The best way to automate project initialization is using the --auto flag, which runs the research, requirements, and roadmap generation workflow non-interactively. This allows product managers or founders to produce scoped requirements and phased roadmaps without manual interaction.

Can I capture project scope and stakeholder constraints without manually formatting markdown files?

Yes, you can capture project scope and stakeholder constraints through guided interactive prompts that automatically generate .planning/PROJECT.md, config.json, REQUIREMENTS.md, ROADMAP.md, and STATE.md. This eliminates manual markdown formatting by producing a structured project configuration.

Does this project planning workflow support non-interactive automation while preserving approval gates?

Yes, the project planning workflow supports an --auto non-interactive flow for generating artifacts while explicitly preserving validation gates, approvals, commits, and routing. This ensures automated project inception still respects necessary review checkpoints.

When do I need to integrate domain research into project requirements generation?

You need to integrate domain research into project requirements generation during project inception when scoping requires evidence-backed context. The Skill optionally collects and organizes research into .planning/research/ to establish grounded requirements and phased roadmaps.

What planning artifacts are generated when initializing a new product or engineering initiative?

Initializing a new product or engineering initiative generates a structured set of planning artifacts: .planning/PROJECT.md, config.json, REQUIREMENTS.md, ROADMAP.md, and STATE.md. These files establish a versioned source of truth for goals, scope, and project state.