openspec-onboard

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

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-onboard-gqadonis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-onboard
Source: https://github.com/GQAdonis/artifact-refiner-skill/tree/main/.kimi-code/skills/openspec-onboard
Command: npx skills add https://github.com/GQAdonis/artifact-refiner-skill --skill openspec-onboard-gqadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Learning a new spec-driven development workflow is hard when documentation is abstract. This Skill teaches the OpenSpec change lifecycle by doing real work in your codebase, walking you from task selection through proposal, specs, design, tasks, implementation, and archiving with explanations at each step. ## Core Features & Use Cases - Guided Workflow Cycle: Walks through all phases of an OpenSpec change—explore, new change, proposal, specs, design, tasks, apply, and archive—with EXPLAIN/DO/SHOW/PAUSE narration. - Codebase Task Discovery: Scans for TODO/FIXME comments, missing error handling, untested functions, and debug artifacts to suggest appropriately scoped starter tasks. - Store-Aware CLI Usage: Discovers registered OpenSpec stores via openspec store list --json and applies --store <id> consistently across commands. - Use Case: A developer new to OpenSpec runs the skill, picks a small real fix in their repo, and completes a full change cycle in about 15-20 minutes while learning each artifact's purpose. ## Quick Start Ask the assistant to walk you through your first OpenSpec change using a small task in your current 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 hands-on?

Run the openspec-onboard skill, which walks you through a full change cycle on a real task in your codebase. It covers explore, proposal, specs, design, tasks, implementation, and archiving with explanations at each phase.

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 suggests 3-4 small scoped tasks. You can also describe your own task, with a soft guardrail against oversized work.

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 skill to begin the guided workflow.

Can I pause an OpenSpec onboarding session and resume later?

Yes, your change is saved on disk, so you can stop at any point. Resume later with openspec-continue-change for artifact creation or openspec-apply-change to jump to implementation if tasks exist.

What artifacts does an OpenSpec change contain?

A change directory holds proposal.md for the why, design.md for the how, a specs/ directory with requirement and scenario definitions, and tasks.md with implementation checkboxes. Archiving moves the completed change into a dated history folder.