openspec-onboard

Name: openspec-onboard
Availability: InStock
Author: wtg42

Guide OpenSpec CLI users through a complete change workflow with proposal, specs, design, tasks, and archive artifacts.

Updated Dec 25, 2025

Search Tags:#workflow #onboarding #cli #openspec #developer #specs #change-management

Ready to run

npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-onboard-wtg42

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-onboard
Source: https://github.com/wtg42/tty-clock-timer/tree/main/.opencode/skills/openspec-onboard
Command: npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-onboard-wtg42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, mentor-like walkthrough for developers unfamiliar with the OpenSpec workflow so they can quickly create, implement, and archive a small, real change in their repository without guesswork.

Core Features & Use Cases

Guided Change Lifecycle: Walks through explore → propose → specs → design → tasks → apply → archive using real repository edits.
Interactive Teaching: Pauses for user approval, explains decisions, and drafts proposal/spec/design content before saving.
Operational Integration: Performs preflight checks for the OpenSpec CLI, scaffolds openspec/changes/<name>/ artifacts, and demonstrates CLI commands for archival and verification.
Use Case: Onboard a new contributor by turning a small TODO or bug into a tracked change with specs and implementation history.

Quick Start

Run a guided OpenSpec onboarding to create and implement a small change in my repository using the OpenSpec CLI.

Frequently Asked Questions about openspec-onboard

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

FAQPage Schema

How do I onboard a new developer to the OpenSpec workflow?▼

You can onboard developers to the OpenSpec workflow using a guided, step-by-step process that walks them through creating, implementing, and archiving a small tracked change in their repository.

What is the best way to create and track a small code change using OpenSpec?▼

The best way to track a small change with OpenSpec is an interactive lifecycle guide that drafts proposal, specs, design, and tasks artifacts before saving them directly into your repository's openspec/changes directory.

Do I need the OpenSpec CLI installed to manage specs and changes?▼

Yes, you need the OpenSpec CLI installed and repository access to run commands like openspec new change and openspec archive for scaffolding and verifying change artifacts.

How does the OpenSpec change management process work end to end?▼

The OpenSpec change management process works by guiding you sequentially through explore, propose, specs, design, tasks, apply, and archive stages while pausing for user approval before saving drafts.

Can I use this guided workflow to turn repository TODOs into tracked changes?▼

Yes, you can turn a small repository TODO or bug into a tracked change by using the interactive workflow to generate the corresponding specs, implementation history, and archive artifacts.