openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
skill-improver
HeyvhuangImprove skills and workflows by analyzing run artifacts and execution logs (events.jsonl/state.json) under runs/ (or OpenSpec changes/). Use when you want to iterate on skills based on real runs: find failure modes, bottlenecks, unclear prompts, missing I/O contracts, and propose concrete edits.
workflow-feature-shipper
HeyvhuangUse when you need to ship a single PR-sized feature end-to-end (plan -> implement -> verify) with artifacts. Ship core product features quickly in a Next.js codebase: turn a feature idea into an executable plan, implement in PR-sized slices, and keep artifacts under runs/ (or OpenSpec changes/ when available). Supports plan-only mode for early scoping. For prototype UI work, include a demo-ready wow moment (animation/micro-interaction) by default unless user opts out.
workflow-ship-faster
HeyvhuangShip Faster end-to-end workflow for small web apps (default: Next.js 16.1.1): idea/prototype → foundation gate → design-system.md → lightweight guardrails + docs → feature iteration → optional Supabase + Stripe → optional GitHub + Vercel deploy → optional AI-era SEO (sitemap/robots/llms.txt). Resumable, artifact-first under runs/ship-faster/ (or OpenSpec changes/). Trigger: ship/launch/deploy/production-ready MVP.
openspec-new-change
SAPStart a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
openspec-continue-change
SAPContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
openspec-ff-change
SAPFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
openspec-archive-change
SAPArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-apply-change
SAPImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-bulk-archive-change
SAPArchive multiple completed changes at once. Use when archiving several parallel changes.
openspec-verify-change
SAPVerify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-onboard
SAPGuided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-sync-specs
SAPSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-explore
SAPEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-archive
Arman-KudaibergenovArchive a completed OpenSpec change and update the specifications.
openspec-proposal
Arman-KudaibergenovЭтот скилл MUST быть вызван когда нужна формальная спецификация изменения: scaffold proposal.md, tasks.md, design.md и spec deltas. SHOULD также вызывать для архитектурных или сквозных изменений, требующих формального отслеживания. Do NOT использовать для быстрого обсуждения идей — используй brainstorm; для только декомпозиции задач — используй write-plan.
openspec-apply
Arman-KudaibergenovImplement an approved OpenSpec change by following tasks.md step by step.
openspec-change-implementation
bacocoImplements L0-1 changes from proposals.
main-workflow-router
bacocoRoutes work to OpenSpec (L0-1) or BMAD (L2-4). Tracks status and guides through phases.
openspec-change-closure
bacocoArchives completed L0-1 changes.
openspec-change-proposal
bacocoCreates lightweight proposals for L0-1 work.
openspec-daem0n-bridge
9thLevelSoftwareBridges OpenSpec (spec-driven development) with Daem0n-MCP memory - auto-imports specs, informs proposals with past outcomes, converts archived changes to learnings
openspec-apply-change
jerome-benoitImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-ff-change
jerome-benoitFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
openspec-verify-change
jerome-benoitVerify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-new-change
jerome-benoitStart a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
openspec-bulk-archive-change
jerome-benoitArchive multiple completed changes at once. Use when archiving several parallel changes.
openspec-sync-specs
jerome-benoitSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-continue-change
jerome-benoitContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
openspec-archive-change
jerome-benoitArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-explore
jerome-benoitEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-onboard
jerome-benoitGuided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-workflows
datenoioOpenSpec proposal creation, validation, and implementation workflows. Use when creating change proposals, implementing specs, or working with OpenSpec conventions.
opsx:ff
jkrummFast-forward through OpenSpec artifact creation. Generates all artifacts (proposal, specs, design, tasks) in one go.
animation-shader
Yuki001READ this skill when implementing or configuring animation-style shaders (Toon/Cel Shaders) — including outlines, rim lighting, toon shading, MatCap, emission, dissolve, hatching, or any stylized rendering effect. Contains preset styles and feature-to-reference mappings for lilToon, Poiyomi, UTS2, RToon, SToon, and ToonShadingCollection. Works as a domain knowledge plugin alongside workflow skills (OpenSpec, SpecKit) or standalone via workflow-standalone.md.
game-architect
Yuki001READ this skill when designing or planning any game system architecture — including combat, skills, AI, UI, multiplayer, narrative, or scene systems. Contains paradigm selection guides (DDD / Data-Driven / Prototype), system-specific design references, and mixing strategies. Works as a domain knowledge plugin alongside workflow skills (OpenSpec, SpecKit) or standalone via workflow-standalone.md.
opsx:apply
jkrummImplement tasks from an OpenSpec change. Works through the task list sequentially.
opsx:continue
jkrummContinue working on an OpenSpec change by creating the next artifact one at a time.
opsx:new
jkrummStart a new OpenSpec change. Use when you want to create a new feature with structured specifications.
Document public APIs with README, TSDoc, and OpenSpec
Saikus08Document public APIs using README, TSDoc, and OpenSpec specs
Rulebook Task Management
hivellmSpec-driven task management for features and breaking changes with OpenSpec-compatible format
openspec-proposal-creation-cn
forztfCreate structured change proposals and specification deltas using an OpenSpec-driven approach. Used for planning features, creating proposals, drafting specifications, introducing new capabilities, or initiating development workflows. Trigger phrases include "openspec proposal", "plan", "create proposal", "plan change", "spec feature", "new feature", "new capability", "new requirement", "add feature planning", "design spec".
openspec-proposal-creation
forztfCreates structured change proposals with specification deltas for new features, breaking changes, or architecture updates. Use when planning features, creating proposals, speccing changes, introducing new capabilities, or starting development workflows. Triggers include "openspec proposal", "create proposal", "plan change", "spec feature", "new capability", "add feature planning", "design spec".
openspec-archiving
Archives completed changes and merges specification deltas into living documentation. Use when changes are deployed, ready to archive, or specs need updating after implementation. Triggers include "openspec archive", "archive change", "merge specs", "complete proposal", "update documentation", "finalize spec", "mark as done".
openspec-context-loading-cn
forztfLoad project context, list existing specs and changes, and search for capabilities and requirements. Used when a user asks about project status, existing specifications, ongoing changes, available capabilities, or needs to discover context. Trigger phrases include "openspec context", "what specs exist", "show changes", "list capabilities", "project context", "find spec", "what does a spec contain", "show spec".
openspec-implementation
forztfImplements approved specification proposals by working through tasks sequentially with testing and validation. Use when implementing changes, applying proposals, executing spec tasks, or building from approved plans. Triggers include "openspec implement", "implement", "apply change", "execute spec", "work through tasks", "build feature", "start implementation".