One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill new-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-development
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/new-development
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill new-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of wasting significant time and resources building unproven new products, tools, or systems that fail to meet real user demand, by enforcing rigorous idea validation before any planning or code is written.

Core Features & Use Cases

  • Greenfield Confirmation Check: Automatically detects if any part of the project already exists as code to route you to the correct development workflow, avoiding wasted effort on the wrong process.
  • YC-Style Idea Validation: Runs six forcing questions via G Stack /office-hours to confirm real demand, pain point severity, and a buildable minimum viable version before any work begins.
  • End-to-End Build Orchestration: Manages the full greenfield build workflow from validated idea to PRD creation, phase planning, TDD execution, code review, QA, and production deployment.
  • Use Case: If you have an idea for a new project management SaaS tool that does not exist yet, this Skill guides you through validating that target users will pay for it, breaking the build into manageable phases, and executing the full build with built-in testing and quality checks.

Quick Start

Use the new-development skill to build your new product, tool, or platform idea from scratch after confirming no existing code for the project exists.

Frequently Asked Questions about new-development

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

FAQPage Schema
How do I validate a greenfield software idea before writing any code?

To validate a greenfield idea before coding, run YC-style demand validation forcing questions to confirm real user demand, pain point severity, and a buildable minimum viable version. This prevents wasting resources on unproven product concepts.

What is the best way to manage end-to-end new product development from scratch?

End-to-end greenfield development is managed by orchestrating the full workflow from validated idea to PRD creation, phase planning, TDD execution, code review, QA, and production deployment. This ensures a structured path from concept to a fully tested live application.

Can I use a greenfield development workflow if some existing code already exists?

Greenfield development workflows are not suitable if existing code, schemas, or APIs are present. A greenfield confirmation check automatically detects any existing codebase to route you to the correct development workflow, avoiding wasted effort on the wrong process.

How do I plan phases for a new SaaS platform build with no existing codebase?

Planning phases for a new SaaS platform involves breaking the validated idea into manageable build stages after PRD creation. This structured phase planning precedes TDD execution and production deployment, ensuring systematic progress tracking for the entire greenfield project.

Does TDD workflow integrate with new product deployment automation?

TDD workflow integrates directly into the greenfield build orchestration, immediately followed by code review, QA, and production deployment automation. This ensures every new product build phase meets quality checks before reaching the production environment.

When should I not use a greenfield development process for a new tool?

You should not use a greenfield development process when your project involves extending an existing codebase, schema, or API. Greenfield workflows exclusively target new product, tool, platform, or application builds with absolutely no pre-existing code to extend.