project-setup

Scaffolds repository instructions, standards, agents, prompts, and skills into a governed development baseline.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill project-setup-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-setup
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/project-setup
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill project-setup-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? New or unstructured repositories lack a consistent agent customization layer, forcing teams to manually create instruction files, standards, prompts, and skill selections before development can begin. ## Core Features & Use Cases - Baseline Scaffolding: Detects the existing stack and creates repository instructions, scoped standards, specialist agents, reusable prompts, and decision records only where none exist. - Skill Selection: Chooses required and suggested skills from the installed catalog matched to the project's actual languages, frameworks, and constraints. - Conflict-Safe Planning: Classifies every planned artifact as create, already-present, or conflict, and never overwrites project-authored content. - Use Case: Point it at an existing repository that has source code but no agent customization layer, and it produces a validated setup plan plus a governed baseline without touching source code. ## Quick Start Ask the agent to set up this repository with the project baseline and generate the setup plan for a new Azure API service.

Frequently Asked Questions about project-setup

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

FAQPage Schema
How do I set up a new repository with agent instructions and standards?

Run the project-setup skill, which detects your languages and frameworks, then creates repository instructions, scoped standards, prompts, agents, and decision records. It writes only files that do not already exist and requires approval before any write.

How do I bring an existing repository up to a governed baseline?

The skill inspects the existing tree first and classifies every planned artifact as create, already-present, or conflict. It appends orchestration routing to existing instructions without removing project-authored content and never modifies source code.

Will project setup overwrite my existing instruction files?

No. The skill stops and reports a conflict when a baseline artifact exists with different project-authored content. It never merges silently and never replaces existing instructions, agents, prompts, or skills.

What does the project setup skill produce as output?

It emits a machine-readable plan at reports/project-setup-plan.json validated against the setup plan schema, plus a Markdown view at reports/project-setup-plan.md. Both record the resulting baseline and skill selections.

When should I not use the project setup skill?

Do not use it for feature implementation, dependency installation, or tool and runtime validation. Tool, runtime, authentication, and debugging checks belong to the development-environment-readiness skill, which runs after setup.