One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-new-project-pear-commerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-new-project
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-new-project
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-new-project-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting a new project often results in scattered context, undefined requirements, and inconsistent planning artifacts that derail team alignment. This skill solves that by gathering deep contextual input upfront and generating standardized, reusable project documentation.

Core Features & Use Cases

  • Standardized Planning Artifacts: Automatically creates core .planning files including PROJECT.md for project context, config.json for workflow preferences, REQUIREMENTS.md for scoped requirements, ROADMAP.md for phased execution plans, and STATE.md for persistent project memory.
  • Flexible Initialization Modes: Supports interactive context gathering via targeted questions, plus an automatic mode for hands-off setup when an idea document is provided.
  • Use Case: For a new software feature, use this skill to collect all relevant project context, define clear scoped requirements, and build a phased roadmap to keep engineering and product teams aligned from kickoff.

Quick Start

Provide your initial project idea or context to the gsd-new-project skill to automatically generate all core planning documents and set up your project workflow.

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 standardized project planning artifacts for new software features?

To generate standardized project planning artifacts, this skill gathers deep contextual input and automatically creates core .planning files like PROJECT.md, REQUIREMENTS.md, and ROADMAP.md. This ensures consistent project initialization and aligned execution plans.

What is the best way to define scoped requirements and phased roadmaps during project kickoff?

The best way to define scoped requirements and phased roadmaps is by using interactive context gathering or an automatic mode. The skill processes your initial project idea to build structured execution plans and generate persistent project state tracking files.

Can I use an existing idea document for project initialization instead of answering interactive questions?

Yes, you can use an existing idea document for project initialization. The automatic mode enables hands-off setup by processing your provided idea document to generate the required .planning configuration and requirements files without interactive questions.

What configuration files are needed to maintain persistent project state tracking?

To maintain persistent project state tracking, the skill creates a STATE.md file alongside config.json for workflow preferences. These files store project memory and ensure repeatable, aligned workflows throughout the software engineering lifecycle.

Does project initialization work without external dependencies for software engineering teams?

Yes, project initialization works without external dependencies. The skill independently eliminates scattered context by gathering upfront input and generating standardized documentation, satisfying the need for repeatable alignment without requiring additional frameworks.