MCPInstall

openspec-onboard

Guided onboarding through the complete OpenSpec workflow using /opsx:onboard, walking the user through a real change in their codebase. Use when the user says "onboard me", "tutorial", "/opsx:onboard", "how does OpenSpec work", or is new to OpenSpec.

Installs
102
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-onboard
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads openspec-onboard automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

OpenSpec Onboard Skill

Use /opsx:onboard for a guided, interactive tutorial through the complete OpenSpec workflow. The tutorial uses the user's actual codebase — finding real improvement opportunities, creating a real change, implementing it, and archiving it.

When to Use

  • First-time OpenSpec users who want a hands-on walkthrough.
  • The user says "onboard", "tutorial", "show me how OpenSpec works".
  • Learning the workflow before using it on real work.

Prerequisites

  • OpenSpec initialized in the project (see openspec-initial).

Workflow

  1. Start onboarding

    • Run /opsx:onboard.
  2. Tutorial phases

    1. Welcome and codebase analysis.
    2. Finding an improvement opportunity (small, safe changes).
    3. Creating a change (/opsx:new).
    4. Writing the proposal.
    5. Creating specs.
    6. Writing the design.
    7. Creating tasks.
    8. Implementing tasks (/opsx:apply).
    9. Verifying implementation.
    10. Archiving the change.
    11. Summary and next steps.
  3. Interactive

    • The agent explains each step as it happens.
    • The user chooses which improvement to work on.
    • The change created is real and can be kept or discarded.

Outputs

  • A complete change cycle (from proposal to archive) using the user's actual codebase.
  • The user has first-hand experience with every OPSX command.

Next Steps

  • Start real work with openspec-new or openspec-explore.

Troubleshooting

  • "Commands not recognized": Ensure OpenSpec is initialized (openspec init). See openspec-initial.
  • Takes too long: The tutorial covers the full workflow; expect 15-30 minutes.

References

FAQ

What does the openspec-onboard skill do?

Guided onboarding through the complete OpenSpec workflow using /opsx:onboard, walking the user through a real change in their codebase. Use when the user says "onboard me", "tutorial", "/opsx:onboard", "how does OpenSpec work", or is new to OpenSpec.

How do I install openspec-onboard?

Run npx skills add https://github.com/full-stack-skills/openspec-skills --skill openspec-onboard in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/openspec-onboard/ (personal) or .claude/skills/openspec-onboard/ (project).

Which AI agents can use openspec-onboard?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is openspec-onboard safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains openspec-onboard?

It is published by full-stack-skills in full-stack-skills/openspec-skills. It has 102 recorded installs.

More from full-stack-skills/openspec-skills

View all →

openspec-apply

full-stack-skills/openspec-skills

Implement tasks from the change using /opsx:apply, working through the task list and checking off items. Use when the user says "implement", "apply the change", "/opsx:apply", or "start coding from tasks".

openspec-new

full-stack-skills/openspec-skills

Start a new OpenSpec change with /opsx:new, creating a change folder with metadata and scaffolding. Use when the user says "start a new change", "new feature", "/opsx:new", or "create an OpenSpec change".

103 installs

openspec-update

full-stack-skills/openspec-skills

Run openspec update to regenerate AI tool instruction files after upgrading the OpenSpec CLI. Use when the user says "update OpenSpec", "openspec update", or "refresh OpenSpec skills/commands".

103 installs

openspec-initial

full-stack-skills/openspec-skills

Run openspec init to initialize OpenSpec in a project directory, creating the openspec/ folder structure and configuring AI tool integrations. Use when the user says "initialize OpenSpec", "openspec init", or "set up OpenSpec in this project".

103 installs

openspec-install

full-stack-skills/openspec-skills

Install the OpenSpec CLI globally via npm, pnpm, yarn, bun, or nix. Use when the user says "install OpenSpec", "set up OpenSpec", or "openspec command not found".

Backend & APIs103 installs

openspec-schema

full-stack-skills/openspec-skills

Create and manage custom workflow schemas using openspec schema init/fork/validate/which. Use when the user says "create a custom workflow", "custom schema", "fork a schema", or wants to define their own artifact types and dependencies.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.