spec-driven-dev

Manages proposals, delta specs, design, and tasks within OpenSpec workflows.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/baobaoyeye/skills --skill spec-driven-dev-baobaoyeye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-dev
Source: https://github.com/baobaoyeye/skills/tree/main/spec-driven-dev
Command: npx skills add https://github.com/baobaoyeye/skills --skill spec-driven-dev-baobaoyeye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @inquirer/core, @inquirer/prompts, chalk, commander, fast-glob, ora, posthog-node, yaml, zod, typescript, and includes scripts (resource) components.

What problem does it solve?

OpenSpec 的规范驱动开发流程需要严格的 artifacts 管理与工作流约束。本 Skill 提供自包含的指南与执行能力,确保从初始化、提案、规格、设计到任务的完整生命周期在规范目录中有序推进。

Core Features & Use Cases

  • 能力覆盖从初始化项目、创建变更提案、制定规范、技术设计及任务规划的完整生命周期,确保目录结构与工作流与 OpenSpec 规范对齐。
  • 支持 OpenSpec 的变更流程(openspec/changes)与 delta 规范输出,便于多团队并行工作与逐步落地。
  • 借助本 Skill 的脚本与模版集成,确保输出的 artifacts(proposal、specs、design、tasks)符合模板结构,且可在需要时扩展引用脚本、参考资料与资产。

Quick Start

To begin, run the OpenSpec init flow to scaffold a spec-driven change and follow prompts to create proposal, specs, design, and tasks.

Frequently Asked Questions about spec-driven-dev

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

FAQPage Schema
How do I manage spec-driven development proposals and delta specs in OpenSpec?

Spec-driven development in OpenSpec coordinates proposals, delta specs, design, and tasks within openspec/specs and openspec/changes folders. It ensures artifact scaffolding follows templates and validates frontmatter for multi-team planning.

What is the OpenSpec change workflow for organizing technical design and tasks?

The OpenSpec change workflow structures technical design and tasks through delta spec outputs in the openspec/changes directory. It allows teams to progressively land changes and work in parallel on the same project.

How to scaffold spec-driven changes and validate frontmatter for proposals?

Scaffolding spec-driven changes validates frontmatter and ensures output artifacts like proposals, specs, design, and tasks conform to template structures. It integrates optional scripts, references, and assets for on-demand operations.

Does spec-driven development work with TypeScript and zod for workflow automation?

Spec-driven development uses TypeScript and zod within its scripts to automate the OpenSpec lifecycle. It provides a self-contained execution capability to ensure directory structures align with OpenSpec standards.

Can I use this spec-driven approach for multi-team parallel work and archive workflows?

This spec-driven approach supports multi-team parallel work and archive workflows by managing delta specs within the openspec/changes folders. It ensures artifact scaffolding follows templates and integrates with optional scripts for operations.

What is the best way to initialize a spec-driven change lifecycle from proposal to tasks?

The best way to initialize a spec-driven change lifecycle is running the OpenSpec init flow to scaffold the change. Follow prompts to create proposals, specs, design, and tasks, ensuring the directory structure aligns with OpenSpec.