spec-workflow

Orchestrate multi-agent spec workflows with status transitions and UUID conversation IDs.

1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/komluk/scaffolding.template --skill spec-workflow-komluk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/komluk/scaffolding.template/tree/main/stacks/_common/.claude/skills/spec-workflow
Command: npx skills add https://github.com/komluk/scaffolding.template --skill spec-workflow-komluk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the entire lifecycle of specification-driven development, ensuring clear communication and coordinated execution across multiple AI agents.

Core Features & Use Cases

  • Orchestrates Multi-Agent Workflows: Manages the flow from initial analysis and design to implementation and verification.
  • Enforces Spec Lifecycle: Tracks and updates the status of development phases (exploring, drafting, implementing, reviewing, complete).
  • Use Case: Automate the process of developing a new feature by having the analyst create a proposal, the architect design it, the developer implement it, and the reviewer verify it, all coordinated through this Skill.

Quick Start

Initiate the spec workflow for a new feature by providing the conversation ID.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
How do I coordinate multiple AI agents for spec-driven development?

Multi-agent spec-driven development is coordinated by orchestrating workflows across defined phases. The system manages status transitions and routes tasks to analyst, architect, developer, and reviewer agents, ensuring structured execution from initial analysis to final verification.

What is the OpenSpec workflow lifecycle for multi-agent orchestration?

The OpenSpec workflow lifecycle is a structured process managing development phases from exploration to completion. It tracks statuses like drafting, implementing, and reviewing, while enforcing UUID conversation IDs to coordinate agents and manage spec file updates within structured directories.

How do I start an OpenSpec workflow for a new feature proposal?

Start an OpenSpec workflow by providing a conversation ID. This initiates the spec-driven development lifecycle, allowing the orchestrator to route the proposal through analyst, researcher, architect, developer, and reviewer agents to automate feature creation.

Does spec-driven development require UUID conversation IDs for agent routing?

Yes, spec-driven development requires UUID conversation IDs to enforce strict agent routing. This ensures traceable communication across multi-agent workflows, allowing the orchestrator to accurately manage status transitions and spec file updates throughout the lifecycle.

What are the status transitions in a spec-driven development workflow?

Status transitions in a spec-driven workflow progress sequentially through exploring, drafting, implementing, reviewing, and complete. The orchestrator manages these phase shifts as tasks pass between analyst, architect, developer, and reviewer agents.

When should I not use a multi-agent orchestration workflow?

Avoid multi-agent orchestration workflows for simple tasks lacking distinct analysis, design, implementation, and review phases. The overhead of managing UUID conversation IDs and status transitions is only justified for complex features requiring coordinated multi-agent execution.