skills.rest
mahmoud20138
mahmoud20138COMMUNITY
Explore all skills by this author →
GitHub

openspec

Manage spec changes with the OpenSpec three-command workflow.

10|2|Updated Mar 8, 2026
Search Tags:#spec-driven#brownfield#openspec#ai-development#iterative-design#opsx#change-proposal
One-click install
npx skills add https://github.com/mahmoud20138/Tradecraft --skill openspec-mahmoud20138
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec
Source: https://github.com/mahmoud20138/Tradecraft/tree/main/plugins/tradecraft/skills/openspec
Command: npx skills add https://github.com/mahmoud20138/Tradecraft --skill openspec-mahmoud20138

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec helps teams adopt a fluid, iterative spec-driven approach for AI-enabled development, replacing rigid upfront specs with ongoing collaboration and evolving blueprints.

Core Features & Use Cases

  • Fluid, iterative spec workflow suitable for brownfield and greenfield projects
  • Propose, design, implement, and archive spec changes using a standard folder layout
  • Works with the /opsx:propose, /opsx:apply, /opsx:archive commands to manage change lifecycle

Quick Start

Initialize a new OpenSpec workflow in your project and start a proposal with /opsx:propose

Frequently Asked Questions about openspec

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

FAQPage Schema
What is iterative spec-driven development for AI projects?▼

Iterative spec-driven development for AI projects replaces rigid upfront specs with a fluid workflow, guiding teams to propose, design, implement, and archive evolving spec changes using a structured folder layout.

Can I use spec-driven workflows for brownfield projects?▼

Yes, you can use spec-driven workflows for brownfield projects. This approach applies to both brownfield and greenfield environments, safely guiding teams through proposing and archiving spec changes.

How do I manage spec change proposals in an AI development workflow?▼

You manage spec change proposals using a three-command workflow: /opsx:propose to start, /opsx:apply to implement, and /opsx:archive to finalize, ensuring repeatable and safe spec iterations.

What is the best way to structure iterative design specs for AI features?▼

The best way to structure iterative design specs is using a standardized folder layout like .openspec/changes/<feature-name>/ containing proposal.md, specs/, design.md, and tasks.md files.

How do I start a new OpenSpec workflow in my project?▼

To start a new OpenSpec workflow, initialize the standard folder layout in your project and begin a proposal using the /opsx:propose command to define your initial spec changes.

Why does AI development need a fluid spec workflow instead of rigid upfront specs?▼

AI development needs a fluid spec workflow because it enables ongoing collaboration and evolving blueprints, replacing rigid upfront specs that cannot adapt to iterative project changes safely.

Related Skills

Explore More Software Engineering Skills→
JNZaderJNZader

sdd-init

Initialize Spec-Driven Development context and generate project structures.

Community
Advanced
ZTE-AICloudZTE-AICloud
52

tasks

Generate dependency-ordered tasks.md from design documents for feature implementation.

Official
Advanced
stepandelstepandel
4

eng-ticket-workflow

Manage software development tickets from triage to pull request submission.

Community
Advanced
langadventurellclangadventurellc

requirements-creation

Convert vague change ideas into structured What/Where/Why/Done ticket specifications.

Official
Basic