openspec-onboard

Guide developers through the OpenSpec workflow to create, document, implement, and archive code changes.

Updated Feb 25, 2026

Search Tags:#workflow #onboarding #implementation #openspec #proposal #specs #change-management

Ready to run

npx skills add https://github.com/futuretea/x-project --skill openspec-onboard-futuretea

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-onboard
Source: https://github.com/futuretea/x-project/tree/main/.claude/skills/openspec-onboard
Command: npx skills add https://github.com/futuretea/x-project --skill openspec-onboard-futuretea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides developers through a complete OpenSpec workflow so they can learn the change lifecycle by doing real work in their repository, turning uncertainty about process into a repeatable rhythm.

Core Features & Use Cases

Interactive Onboarding: Step-by-step narration through exploration, proposal, specs, design, tasks, implementation, and archive phases.
Codebase-aware Tasks: Scans the repository for small starter tasks (TODOs, missing tests, debug artifacts) and helps pick an appropriate slice of work.
Artifact Management: Creates and saves structured artifacts under openspec/changes (proposal, specs, design, tasks) and automates archival of completed changes.
Implementation Guidance: Walks through implementing tasks with light narration, spec-driven checks, and git-aware operations.

Quick Start

Start the OpenSpec onboarding by initializing OpenSpec in your repository if needed and then run /opsx:new to create a change and begin the guided cycle.

Frequently Asked Questions about openspec-onboard

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

FAQPage Schema

What is the OpenSpec workflow for proposing and implementing code changes?▼

The OpenSpec workflow guides developers through a structured change lifecycle: scanning code, drafting proposals, creating specs, designing solutions, breaking down tasks, implementing changes, and archiving completed artifacts under openspec/changes in the repository.

How do I start using OpenSpec to document and implement a new code change?▼

Initialize OpenSpec in your repository and run /opsx:new to create a change. The onboarding cycle then guides you step-by-step through proposal, specs, design, tasks, implementation, and archive phases.

Do I need the openspec CLI installed to use this onboarding workflow?▼

Yes, the openspec CLI must be available in your environment. You also need read and write access to the repository and its git history to create artifacts under openspec/changes and save changes.

Can OpenSpec help me find small starter tasks like TODOs or missing tests in my repository?▼

Yes, the onboarding workflow scans your codebase for small starter tasks, including TODOs, missing tests, and debug artifacts, helping you pick an appropriate slice of work to learn the change lifecycle.

What is the best way to manage OpenSpec proposal and spec artifacts during development?▼

OpenSpec manages artifacts by creating and saving structured files under openspec/changes, including proposals, specs, designs, and tasks. It also automates the archival of completed changes to maintain repository hygiene.

Are there limitations to using OpenSpec for onboarding large scale code changes?▼

This workflow targets small code changes suitable for onboarding. It scans for small starter tasks like TODOs and missing tests, so it may not fit large-scale architectural modifications requiring extensive change management.