openspec-onboard

Guides users through a complete OpenSpec change workflow cycle with narrated phases.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-onboard-capella-hotel-group
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-onboard
Source: https://github.com/capella-hotel-group/capella-hotel-group-poc/tree/main/.github/skills/openspec-onboard
Command: npx skills add https://github.com/capella-hotel-group/capella-hotel-group-poc --skill openspec-onboard-capella-hotel-group

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Learning a new spec-driven development workflow is hard without hands-on practice. This Skill teaches the OpenSpec workflow by walking you through a real change cycle in your own codebase, from task selection to archiving, with explanations at every step. ## Core Features & Use Cases - Guided Workflow Tutorial: Walks through the full OpenSpec cycle—explore, propose, spec, design, tasks, apply, and archive—using a real task in your codebase. - Codebase Task Discovery: Scans for TODOs, missing error handling, untested functions, and debug artifacts to suggest appropriately scoped starter tasks. - Artifact Generation: Creates proposal.md, specs, design.md, and tasks.md in the openspec/changes directory with requirement/scenario formatting. - Use Case: A developer new to spec-driven development runs the onboarding, picks a small fix like removing console.log statements, and completes their first full change cycle in about 20 minutes. ## Quick Start Ask the assistant to walk you through your first OpenSpec change using a small task in this repository.

Frequently Asked Questions about openspec-onboard

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

FAQPage Schema
How do I learn the OpenSpec workflow?▼

Run the onboarding skill, which walks you through a complete change cycle using a real task in your codebase. It covers exploring the problem, creating a change, writing proposal, specs, design, and tasks, then implementing and archiving.

How do I create an OpenSpec change with proposal and specs?▼

Use the openspec new change command with a kebab-case name, then fill in proposal.md, specs under specs/<capability>/, design.md, and tasks.md. The onboarding skill demonstrates each artifact with drafts you approve before saving.

Does OpenSpec onboarding require the CLI installed?▼

Yes, the openspec CLI must be installed before starting. The skill runs a preflight check with openspec --version and stops with an install prompt if the CLI is not found.

What happens if I stop an OpenSpec change halfway through?▼

Your change is saved in openspec/changes/<name>/ and nothing is lost. You can resume later with /opsx:continue to finish artifacts or /opsx:apply to jump to implementation if tasks already exist.

What size task should I pick for my first OpenSpec change?▼

Pick a small task of one to two files and roughly 20-30 lines, such as fixing a TODO or removing debug statements. The skill includes a scope guardrail that suggests slicing larger tasks, though you can override it.