onboard

Generate project configuration and CI workflows during interactive repository onboarding.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/rnwolfe/forge --skill onboard-rnwolfe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/rnwolfe/forge/tree/main/.claude/skills/onboard
Command: npx skills add https://github.com/rnwolfe/forge --skill onboard-rnwolfe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The onboard skill streamlines the tedious and error-prone process of initializing a new repository with forge's autonomous development pipeline by interactively generating project documentation, configuration, CI workflows, and GitHub setup guidance.

Core Features & Use Cases

  • Interactive multi-phase onboarding: Guides the user through identity, tech stack, architecture, scaffolding, MVP issues, and GitHub setup, producing committed artifacts at each phase.
  • Automated configuration generation: Populates forge.toml, .github/workflows/ci.yml, CODEOWNERS, CLAUDE.md, and docs/internal/VISION.md with project-specific content.
  • Verification and guardrails: Checks for gh CLI, repository state, existing CLAUDE.md/VISION.md conflicts, and offers safe reset and manual steps while asking for confirmation before destructive actions.
  • Use case: Quickly bootstrap a new repository from the forge template to produce a production-ready CI pipeline, documentation, and issue backlog for autonomous agents to act on.

Quick Start

Run /onboard to start an interactive onboarding session that generates CLAUDE.md, VISION.md, forge.toml, and CI workflows while verifying repository state.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I bootstrap a new GitHub repository with CI workflows and documentation?

Interactive project bootstrapping automates repository initialization by generating CLAUDE.md, VISION.md, forge.toml, CODEOWNERS, and CI workflows. It guides you through identity, tech stack, architecture, scaffolding, MVP issues, and GitHub setup across multiple phases.

What is the best way to generate project configuration files for a forge template repository?

Generating project configuration files for a forge template is best handled by interactive onboarding sessions that populate forge.toml and CI workflows with project-specific content. This approach produces committed artifacts at each phase while verifying repository state.

Do I need the gh CLI installed to set up repository labels and branch protections?

Yes, you need the gh CLI installed to set up repository labels and protections during onboarding. The process verifies gh CLI availability and git history before performing GitHub operations, enforcing guardrails for safe commits.

Can I overwrite an existing CLAUDE.md or VISION.md during project onboarding?

Project onboarding checks for existing CLAUDE.md and VISION.md conflicts before writing. It offers safe reset and manual steps while asking for confirmation before destructive actions, preventing accidental overwrites of your documentation.

What files are automatically generated when bootstrapping a repository from the forge template?

Bootstrapping a repository from the forge template automatically generates CLAUDE.md, docs/internal/VISION.md, forge.toml, .github/workflows/ci.yml, CODEOWNERS, and repository labels and protections, creating a production-ready CI pipeline and issue backlog.

Why does interactive onboarding verify git history before applying GitHub repository protections?

Interactive onboarding verifies git history and repository state to enforce guardrails for safe commits and GitHub operations. This prevents applying branch protections or labels to repositories with conflicting states or missing prerequisites.