project-onboarding

Scaffold missing project coordination files without overwriting existing content.

5|2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill project-onboarding-dbc-oduffy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-onboarding
Source: https://github.com/dbc-oduffy/coordinator-claude/tree/main/plugins/coordinator/skills/project-onboarding
Command: npx skills add https://github.com/dbc-oduffy/coordinator-claude --skill project-onboarding-dbc-oduffy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a new repository from scratch is error-prone and often misses essential conventions, trackers, and documentation structure needed for reliable plan review and execution handoffs.

Core Features & Use Cases

  • Detects existing coordination infrastructure: surveys standard files and directories without overwriting them, and turns missing infrastructure into a clear “what to create next” report.
  • Cold-starts a project with PM-controlled scope: asks the PM to ratify project identity and initial workstreams, then scaffolds only the meaningful day-1 artifacts (CLAUDE.md, tracker, docs index, and safety-related gitignore/hook).
  • Supports runtime stack sanity-checking: classifies project type (game-dev, web-dev, data-science, general) via manifests and an external marker scan to inform conventions and routing.

Quick Start

Run the coordinator skill in your repo root when you start a new project or when /update-docs reports tracker_missing so the skill can scaffold the project’s coordination baseline.

Frequently Asked Questions about project-onboarding

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

FAQPage Schema
How do I scaffold project tracking files for a new repository?▼

Scaffolding project tracking for a new repository involves detecting existing coordination artifacts and generating missing day-1 files like CLAUDE.md and docs/project-tracker.md. This process preserves existing content while establishing a PM-EM compatible project skeleton.

What files are needed for PM-EM project coordination on day one?▼

PM-EM project coordination requires CLAUDE.md, docs/project-tracker.md, docs/README.md, and baseline git safety configuration. These files form the day-1 tracker and convention structure needed for reliable plan review and execution handoffs.

Can I run project onboarding without overwriting existing documentation in my repo?▼

Yes, project onboarding surveys standard files and directories without overwriting existing content. It detects current coordination infrastructure and only scaffolds the meaningful artifacts that are reported as missing.

How does a project tracker detect whether a repository is set up for game-dev, web-dev, or data-science?▼

Project tracker detection classifies project type via manifests and an external runtime marker scan. This stack sanity-checking informs conventions and routing for game-dev, web-dev, data-science, or general project contexts.

When should I initialize a project coordination baseline in my repository?▼

You should initialize a project coordination baseline when a repo lacks a standard CLAUDE/docs/tasks structure, when tracker_missing is reported during an update, or on the first coordinator plugin run for marketplace users starting a new project.

Does project onboarding work for cold-starting a project with PM-controlled scope?▼

Yes, project onboarding cold-starts a project by asking the PM to ratify project identity and initial workstreams. It then scaffolds only the day-1 artifacts required to support the defined workstream planning and PM-EM workflow.