che-onboarding

Creates and maintains a human-curated project registry of product context, architecture, and roadmap files.

Updated May 12, 2026
One-click install
npx skills add https://github.com/laionazeredo/che-ai --skill che-onboarding-laionazeredo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: che-onboarding
Source: https://github.com/laionazeredo/che-ai/tree/main/skills/che-onboarding
Command: npx skills add https://github.com/laionazeredo/che-ai --skill che-onboarding-laionazeredo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated specs are often technically correct but product-misaligned because agents lack business context like personas, hard business invariants, and planned scope. This Skill captures that human knowledge in a shared registry stored outside the worktree so every downstream spec starts from the same product truth. ## Core Features & Use Cases - Structured product registry: Generates and interactively fills product_context.md (8 mandatory sections), roadmap.md, and the manual portion of architecture.md under $CHE_PROJECT_DIR. - Three execution modes: --show for read-only summaries, default interactive mode for section-by-section confirmed updates, and --bootstrap to scaffold empty [PENDING] templates on first run. - Storage boundary enforcement: Resolves canonical paths via the che CLI, asserts the registry stays outside the user worktree, and writes atomically with audit entries appended to registry.jsonl. - Use Case: Before running /che-spec on a project's first feature, run this Skill to record personas, non-negotiable business rules, integrations, and out-of-scope features so the generated spec injects that context automatically. ## Quick Start Ask the agent to run che-onboarding in bootstrap mode to create the product context, architecture, and roadmap registry files for this project.

Frequently Asked Questions about che-onboarding

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

FAQPage Schema
How do I give an AI coding agent product context before generating specs?▼

Run this Skill to fill a product_context.md registry with personas, business invariants, integrations, and scope limits. Downstream spec generation reads sections on personas, hard invariants, and out-of-scope items and injects them into every spec.

What is the difference between che-onboarding and che-xray?▼

che-xray is automatic and reads code to build a technical project profile, while che-onboarding is the human side that captures intent, business context, roadmap, and people. They are complementary, and onboarding is typically run after xray.

Where does the project registry get stored?▼

The registry lives outside the user worktree under $CHE_SESSIONS_ROOT/.registry/projects/<slug>/, resolved via the che CLI compute_paths helper. It never creates files inside the worktree unless the user explicitly requests a verbatim copy.

Can I create the registry files without answering interactive questions?▼

Yes, use --bootstrap mode to create product_context.md, architecture.md, and roadmap.md with empty [PENDING] template sections. You can then fill them manually or through a later interactive session.

What happens if product context is missing when a spec is generated?▼

The spec workflow checks for product_context.md first. If it is missing in a project that already has worktrees and commits, the spec begins with a warning recommending you run che-onboarding to reduce product ambiguity.