openspec-workflow

Guide OpenSpec changes from artifact creation through Fabro implementation and archival.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/thistleknot/skills --skill openspec-workflow-thistleknot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-workflow
Source: https://github.com/thistleknot/skills/tree/main/openspec-workflow
Command: npx skills add https://github.com/thistleknot/skills --skill openspec-workflow-thistleknot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, fabro, gh, git, and includes references (resource) components.

What problem does it solve?

It standardizes how you create, review, implement, and archive spec-driven changes using OpenSpec for specification and Fabro for implementation, so product work can move from intent to verified code reliably.

Core Features & Use Cases

  • Explore mode (thinking partner): Draft and iterate OpenSpec artifacts without implementing code, supporting clarification during a change.
  • Propose (one-step artifact creation): Generate proposal/design/specs/tasks in the correct dependency order for a new change and keep it consistent with OpenSpec rules.
  • Apply (task-by-task implementation): Execute pending tasks from an existing OpenSpec change using Fabro, updating progress while pausing on ambiguity or blockers.
  • Archive (completion + spec sync): Move completed changes to archive and optionally sync delta specs into main specs with guardrails.
  • Full lifecycle orchestration: Cover the OpenSpec + Fabro workflow including prerequisites, app directory conventions, verification gates, optional browser-based UI testing, and PR/issue linkage.

Quick Start

Provide a kebab-case change name to an AI operator and run an OpenSpec-driven propose step, then implement with the Fabro generic-build workflow and finish by archiving after verification.

Frequently Asked Questions about openspec-workflow

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

FAQPage Schema
How do I run spec-driven development workflows from proposal to implementation?

Spec-driven development workflows run end-to-end by orchestrating OpenSpec artifact creation, Fabro task execution, verification gates, and final archival to move product intent into verified code reliably.

How do I generate OpenSpec proposal, design, specs, and tasks in the correct dependency order?

Generating OpenSpec artifacts uses a propose step that creates proposal, design, specs, and tasks sequentially, enforcing strict artifact dependency ordering and OpenSpec rule consistency for a new change.

Do I need git and gh tooling to automate repository implementation pipelines with Fabro?

Automating repository implementation pipelines with Fabro requires git and gh tooling alongside openspec to execute pending tasks, track progress, and maintain PR and issue metadata conventions.

What is the best way to execute pending OpenSpec tasks while pausing on ambiguity or blockers?

Executing pending OpenSpec tasks uses Fabro within an apply step to implement task-by-task, continuously updating progress while automatically pausing execution when encountering ambiguity or blockers.

Can I sync delta specs into main specs after archiving completed OpenSpec changes?

Syncing delta specs into main specs occurs during the archive step after moving completed OpenSpec changes, applying guardrails to ensure consistent specification updates across the repository.

Does spec-driven development lifecycle orchestration support browser-based UI testing and verification?

Spec-driven development lifecycle orchestration supports optional browser-based UI testing and verification gates after Fabro implementation, ensuring completed changes meet quality standards before archival.