onboard

Guide builders through the Vibe Cartographer onboarding flow to generate planning documents.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/estevanhernandez-stack-ed/vibe-cartographer --skill onboard-estevanhernandez-stack-ed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/estevanhernandez-stack-ed/vibe-cartographer/tree/main/plugins/vibe-cartographer/skills/onboard
Command: npx skills add https://github.com/estevanhernandez-stack-ed/vibe-cartographer --skill onboard-estevanhernandez-stack-ed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboard launches the entire Vibe Cartographer workflow, welcoming the builder, gathering context, migrating any existing profiles, and initializing planning documents so downstream steps can tailor the experience to the person and project.

Core Features & Use Cases

  • Interactive, guided interview that surfaces name, role, goals, origin, design direction, and experience.
  • Generates planning artifacts such as docs/builder-profile.md, and seeds outputs for /scope, /prd, /spec, /checklist, and initial artifacts.
  • Performs unified-profile loading, including migration from legacy paths, and runs a memory-decay check to surface stale preferences when appropriate.
  • Outputs artifacts and hands off to the next command in the chain, while logging context and friction for later reflection.

Quick Start

Begin the guided interview by saying /onboard to start the process and generate the initial builder profile and planning docs.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I convert an idea into a structured project plan using an interactive interview?

To convert an idea into a structured project plan, this onboarding workflow uses an interactive guided interview to gather your name, role, goals, and design direction, then generates planning artifacts and seeds downstream commands like /scope and /prd.

What is the best way to initialize planning docs and a builder profile for a new project?

The best way to initialize planning docs is through an onboarding flow that generates a builder-profile.md file, manages session context, and seeds initial artifacts for downstream specification and checklist generation.

How does context-management handle stale preferences and legacy builder profiles?

Context-management handles stale preferences by performing a memory-decay check and loading unified profiles, including optional migration from legacy paths, to ensure downstream planning documents reflect current builder preferences.

Can I run project onboarding autonomously without an interactive interview?

Yes, you can run project onboarding autonomously, as the workflow ensures both interactive and autonomous runs can produce artifacts while capturing friction and preferences for future retrospectives.

What downstream commands are seeded after generating the initial project planning documents?

After generating initial project planning documents, the onboarding flow seeds downstream commands including /scope, /prd, /spec, and /checklist, handing off context to the next command in the planning chain.