new-project

Scaffolds a private CTO home and dev repos locally, then prints git and gh publish commands.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill new-project-apireno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-project
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/new-project
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill new-project-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a new multi-repo project under an agent-orchestrated workflow requires copying the orchestration mechanism, separating private project IP from the public template, registering repos, and wiring dev-team configuration — all repetitive and error-prone when done by hand. ## Core Features & Use Cases - CTO Home Scaffolding: Copies the template mechanism into a new private <project>-cto directory, adapts CLAUDE.md, and creates IP directories for PRDs, ADRs, and handoffs. - Greenfield or Adopt Modes: Either scaffolds brand-new dev repos with dev-team settings and hooks, or wires the CTO home to an existing fleet after a mono-repo split. - Local-Only Safety: Writes everything to disk and prints the exact gh repo create and git commands to publish — nothing is pushed or created on GitHub automatically. - Use Case: After splitting a mono-repo into multiple services, run the skill in adopt mode to stand up a private CTO home that registers the existing repos in projects.yaml. ## Quick Start Ask the agent to create a new project named acme with repos acme-core and acme-web using the new-project skill.

Frequently Asked Questions about new-project

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

FAQPage Schema
How do I set up a new multi-repo project with a CTO home?

Run the new-project skill with a project name and a comma-separated repo list, for example with --repos=acme-core,acme-web. It scaffolds a private <project>-cto directory and the dev repos locally, then prints the git and gh commands to publish them.

How do I adopt existing repos after a mono-repo split?

Use the --adopt flag, which wires the new CTO home to repos already registered in projects.yaml instead of scaffolding new ones. It also prints optional commands to push the dev-team mechanism into each existing repo.

Does the new-project skill push anything to GitHub automatically?

No. The skill only writes files locally and prints the exact gh repo create and git commands for you to run. Publishing is deliberately manual because creating remote repos is irreversible and outward-facing.

What review engine options does the skill configure?

It offers kimi (a cross-family reviewer via OpenRouter requiring an API key), subagent (free in-session reviews), and handoff (a separate interactive Claude window). The choice is applied to the CTO home and every scaffolded dev repo via set-review-engine.sh.

What happens if the target CTO home directory already exists?

The skill refuses to overwrite it and exits with an error. You must remove the existing directory or choose a different project name before rerunning.