openspec-onboard

Guides users through a complete OpenSpec change workflow with narrated phases and real codebase tasks.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/firstsun-dev/skills --skill openspec-onboard-firstsun-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-onboard
Source: https://github.com/firstsun-dev/skills/tree/main/plugins/spec-driven-development/skills/openspec-onboard
Command: npx skills add https://github.com/firstsun-dev/skills --skill openspec-onboard-firstsun-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Learning a spec-driven development workflow is hard when documentation is abstract. This Skill teaches the OpenSpec change lifecycle by walking you through a real task in your own codebase, explaining each artifact as it is created. ## Core Features & Use Cases - Guided Workflow Cycle: Walks through explore, change creation, proposal, specs, design, tasks, implementation, and archiving with EXPLAIN → DO → SHOW → PAUSE narration. - Codebase Task Discovery: Scans for TODO/FIXME comments, missing error handling, untested functions, and debug artifacts to suggest small starter tasks. - Scope Guardrails: Gently steers oversized tasks toward smaller slices while respecting user choice, and handles mid-session exits gracefully. - Use Case: A developer new to OpenSpec runs the onboarding, picks a small fix from the suggestions, and completes a full change cycle—proposal through archive—in about 15-20 minutes while learning every command. ## Quick Start Ask the agent to walk you through your first OpenSpec change using a small task in your codebase.

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 for the first time?▼

Run the openspec-onboard skill, which walks you through a full change cycle on a real task in your codebase. It narrates each phase—explore, proposal, specs, design, tasks, apply, archive—so you learn by doing in about 15-20 minutes.

How does OpenSpec onboarding pick a task to work on?▼

It scans your codebase for TODO/FIXME comments, missing error handling, untested functions, any types, and debug statements, then presents 3-4 small suggestions. You can also describe your own task, with a soft guardrail against oversized scope.

Does openspec-onboard require the OpenSpec CLI installed?▼

Yes, the skill checks for the openspec CLI in a preflight step and stops if it is not installed. Install the CLI first, then rerun the onboarding command.

Can I stop an OpenSpec onboarding session midway?▼

Yes, the skill handles graceful exits. Your change is saved at its changeRoot, and you can resume later with /openspec-continue-change or jump to implementation with /openspec-apply-change.

What artifacts does an OpenSpec change contain?▼

A change contains proposal.md (why), specs/ (testable requirements in WHEN/THEN format), design.md (technical decisions), and tasks.md (implementation checklist). After completion, the change is archived as decision history.