skills.rest
bartoszwarzocha
bartoszwarzochaCOMMUNITY
Explore all skills by this author →
GitHub

openspec-workflow

Automate OpenSpec change request creation, tracking, and closing workflows.

Updated Oct 25, 2025
Search Tags:#workflow#templates#versioning#openspec#task-management#openspec-changes
One-click install
npx skills add https://github.com/bartoszwarzocha/kalahari --skill openspec-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-workflow
Source: https://github.com/bartoszwarzocha/kalahari/tree/main/.claude/skills/openspec-workflow
Command: npx skills add https://github.com/bartoszwarzocha/kalahari --skill openspec-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides OpenSpec task management: folder structure, numbering, templates, status lifecycle, and progress tracking.

Core Features & Use Cases

  • Folder Structure: openspec/changes/NNNNN-name with proposal.md and tasks.md
  • Numbering: determine the next 5-digit NNNNN change number
  • Templates: proposal.md and tasks.md generation
  • Status Lifecycle: PENDING → IN_PROGRESS → DEPLOYED
  • Creating/Tracking/Closing: end-to-end workflow guidance

Quick Start

Create a new OpenSpec entry by numbering the next change and generating proposal.md and tasks.md.

Frequently Asked Questions about openspec-workflow

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

FAQPage Schema
How do I set up a structured workflow for managing OpenSpec changes from creation to deployment?▼

OpenSpec workflow automates task management by establishing a standardized folder structure (openspec/changes/NNNNN-name), assigning 5-digit incremental change numbers, and generating proposal.md and tasks.md templates. This ensures consistent tracking through the PENDING → IN_PROGRESS → DEPLOYED lifecycle with built-in progress reporting.

What's the best way to organize change request templates and numbering for large-scale task management?▼

The workflow implements automatic 5-digit change numbering, folder layouts, and dual-template schemas (proposal.md and tasks.md) that standardize how change requests are created, tracked, and closed. This removes manual numbering errors and ensures every change follows the same structure and status transitions.

Can I use this for tracking task lifecycle stages and generating progress reports automatically?▼

Yes. The workflow manages the complete status lifecycle from PENDING through IN_PROGRESS to DEPLOYED, with built-in progress tracking and reporting across all active change requests. It eliminates manual status updates by enforcing consistent folder and file organization.

How do I determine the next change number when creating a new OpenSpec entry?▼

The workflow automatically determines the next available 5-digit NNNNN change number by analyzing existing openspec/changes/ directories, preventing conflicts and maintaining sequential ordering across all your change requests.

What happens if I need to close or deploy a change request—does the workflow handle status transitions?▼

The workflow guides end-to-end management including closing change requests. It enforces the PENDING → IN_PROGRESS → DEPLOYED status lifecycle, ensuring all transitions are tracked and documented through the proposal.md and tasks.md structure.

Related Skills

Explore More Product & Management Skills→
inflexa-aiinflexa-ai
29

openspec-new-change

Scaffold new change directories and manage artifact dependencies with openspec CLI.

Official
Intermediate
rkz91rkz91
264

pmstudio-comms

Generate stakeholder communications in Markdown from project context.

Community
Intermediate
mjrtlmjrtl

Process Tasks

Execute task lists sequentially with test-before-commit and conventional commits.

Community
Intermediate
aaaa47080aaaa47080
4

architecture-decision-records

Records architectural decisions with context, alternatives, rationale, and consequences in a structured format.

Community
Advanced