OpenSpec Workflow

Generate proposal, requirements, design, and task documents via workflow commands.

9|3|Updated Apr 16, 2024

Search Tags:#workflow #planning #development #documentation #spec #tasks

Ready to run

npx skills add https://github.com/keiretsu-labs/kubernetes-manifests --skill openspec-workflow-keiretsu-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: OpenSpec Workflow
Source: https://github.com/keiretsu-labs/kubernetes-manifests/tree/main/openclaw/workspaces/main/skills/openspec
Command: npx skills add https://github.com/keiretsu-labs/kubernetes-manifests --skill openspec-workflow-keiretsu-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of planning and documenting new features or changes, ensuring clarity from initial proposal to implementation readiness.

Core Features & Use Cases

Structured Documentation: Generates proposal, requirements, design, and task documents.
Workflow Commands: Provides commands like /opsx:new, /opsx:ff, /opsx:apply, and /opsx:archive to manage the development lifecycle.
Use Case: When a product manager wants to add a new feature, they can use this Skill to initiate the /opsx:new command, which sets up all necessary documentation templates for the engineering team to fill out.

Quick Start

Use the OpenSpec skill to create a new change folder for a feature called 'user-authentication'.

Frequently Asked Questions about OpenSpec Workflow

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

FAQPage Schema

How do I structure feature planning and documentation from proposal to implementation?▼

Spec-driven development structures feature planning by generating proposal, requirements, design, and task documents. This enforces a clear lifecycle from initial ideation to implementation readiness using defined workflow commands.

What workflow commands are used to manage the software development lifecycle?▼

The development lifecycle is managed using command-line interface commands like /opsx:new, /opsx:ff, /opsx:apply, and /opsx:archive. These commands transition features through iterative planning and documentation stages.

How do I set up templates for a new software feature change?▼

To set up documentation templates for a new feature, initiate the /opsx:new command. This creates a dedicated change folder and provides all necessary structured templates for the engineering team to fill out.

What is the best way to break down design documents into actionable engineering tasks?▼

Breaking down design documents into actionable engineering tasks is handled by the spec-driven workflow. It transitions structured design documents into defined task breakdowns, ensuring implementation readiness and clarity.

Can I use this spec-driven workflow for iterative planning without external dependencies?▼

Yes, this spec-driven workflow operates without external dependencies. It uses an internal command-line interface and references component to enforce structured development lifecycle management independently.

When should I not use a structured spec-driven development workflow?▼

Spec-driven workflows should be avoided for rapid prototyping or unstructured changes that bypass formal documentation. It enforces a structured approach requiring proposal, requirements, and design documents before implementation.