openspec-onboard

Guide users through OpenSpec workflow phases from task selection to archiving.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-onboard-jacobcy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-onboard
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/.github/skills/openspec-onboard
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill openspec-onboard-jacobcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers and teams learn and complete a full OpenSpec workflow by guiding them through selecting a small code change, drafting proposal/specs/design/tasks, implementing the work in the codebase, and archiving the decision record so knowledge is preserved.

Core Features & Use Cases

  • Guided, phase-driven onboarding: Walks users through Preflight, Explore, New Change, Proposal, Specs, Design, Tasks, Apply (implementation), and Archive phases with pause points for confirmation.
  • Real codebase interactions: Scans the repository for quick tasks, creates openspec/changes/<name> artifacts, drafts proposal/specs/design/tasks, and instructs stepwise implementation and archival.
  • Teaching-first flow: Emphasizes explanation, scope guardrails, and safe exits so users learn the OpenSpec rhythm while doing actual work.
  • Use case: A developer wanting to learn OpenSpec can pick a small fix, produce testable specs, implement the change, and archive the decision in ~15–30 minutes.

Quick Start

Use the openspec-onboard skill to guide me through creating and applying a small OpenSpec change from task selection to archiving.

Frequently Asked Questions about openspec-onboard

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

FAQPage Schema
How do I create and apply a change using OpenSpec in my repository?

To create an OpenSpec change, you select a small task, draft proposal/specs/design/tasks artifacts in openspec/changes, implement the code edits, and archive the decision record. This guided workflow ensures changes are testable and preserved.

What is the OpenSpec workflow process for managing code changes?

The OpenSpec workflow process is a phase-driven cycle turning ideas into archived changes. It involves Preflight, Explore, New Change, Proposal, Specs, Design, Tasks, Apply, and Archive phases, with interactive pause points for user confirmation.

Do I need the openspec CLI installed to manage specs in my local codebase?

Yes, you need the openspec CLI available in your environment to manage specs in your local codebase. The workflow requires git-aware scanning and creates artifacts in the openspec/changes directory.

How long does it take to learn OpenSpec by doing a real codebase change?

Learning OpenSpec by doing a real codebase change takes about 15 to 30 minutes. A developer can pick a small fix, produce testable specs, implement the change, and archive the decision record within this timeframe.

Can I use OpenSpec to draft design and task documents before implementation?

Yes, you can use OpenSpec to draft design and task documents before implementation. The workflow explicitly includes phases for drafting proposals, specs, designs, and tasks before applying the actual code edits.

What is the best way to preserve decision records for small code fixes?

The best way to preserve decision records for small code fixes is archiving them through the OpenSpec workflow. It guides you through implementation and archives the change, ensuring knowledge is preserved in the repository.