openspec-onboard

Guide users through the OpenSpec change lifecycle from discovery to archiving.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-onboard-guillaumejay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-onboard
Source: https://github.com/guillaumejay/FileIndexer/tree/main/.gemini/skills/openspec-onboard
Command: npx skills add https://github.com/guillaumejay/FileIndexer --skill openspec-onboard-guillaumejay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec onboarding can guide developers through a complete, hands-on workflow, turning a nascent project into a well-documented, reproducible change lifecycle.

Core Features & Use Cases

  • Step-by-step onboarding: Explore, create a change, draft a proposal, define specs and design, plan tasks, implement, and archive to preserve history.
  • Interactive teaching: Real-time narration while making actual codebase changes within a project.
  • Reproducible workflow: Each change is organized under openspec/changes with artifacts and traceability for future reference.

Quick Start

Run the onboarding flow to create a new OpenSpec change and follow the guided phases from welcome to archive.

Frequently Asked Questions about openspec-onboard

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

FAQPage Schema
How do I document a codebase change lifecycle from problem discovery to archiving?

A structured change lifecycle workflow guides you step-by-step through problem discovery, proposal drafting, spec creation, task planning, implementation, and archiving. It organizes artifacts under openspec/changes to preserve history and ensure traceability.

What is the OpenSpec workflow for managing software project changes?

The OpenSpec workflow is a structured change-management process using phases like Explore, Proposal, Specs, Design, Tasks, Apply, and Archive. It enforces phase transitions and frontmatter-based metadata to maintain reproducible documentation across software projects.

Can I use this guided onboarding workflow for software projects of varying sizes?

Yes, the onboarding workflow applies to software projects of varying sizes. It automates the end-to-end change lifecycle, providing interactive, real-time narration while making actual codebase changes to ensure consistent documentation practices.

How do I structure proposals and specs before implementing codebase changes?

You structure proposals and specs by following the guided workflow phases from Proposal to Specs to Design. The process enforces frontmatter-based skill metadata and phase transitions, ensuring artifacts are documented under openspec/changes before implementation begins.

Does this change management workflow preserve a changelog of completed tasks?

Yes, the workflow preserves a changelog through non-destructive guidance and an Archive phase. Completed changes are organized under openspec/changes with artifacts, ensuring full traceability and reproducible history for future reference across the project.

What are the limitations of using a phase-transition workflow for coding changes?

The phase-transition workflow requires strict sequential progression through Explore, Proposal, Specs, Design, Tasks, Apply, and Archive. This enforced structure may add overhead for trivial coding changes that do not require full documentation or formal change-management artifacts.