openspec-workflow

Document and enforce an OpenSpec-backed workflow for QRSPI changes.

2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/lotea-be/qrspi --skill openspec-workflow-lotea-be
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-workflow
Source: https://github.com/lotea-be/qrspi/tree/main/claude/skills/openspec-workflow
Command: npx skills add https://github.com/lotea-be/qrspi --skill openspec-workflow-lotea-be

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec-backed workflow management for QRSPI changes, providing a repeatable structure to persist, map, and audit artifacts across stages while aligning with canonical templates and per-change folders.

Core Features & Use Cases

  • Defines a standard folder layout under openspec/changes/<change-id>/ for each change.
  • Maps QRSPI stages to OpenSpec artifacts (questions, research, design, proposal, specs, slices, tasks, archive) and explains authorship and workflow.
  • Provides canonical artifact shapes and templates, enabling consistent downstream tooling and audits.

Quick Start

Run /qrspi:init to bootstrap the openspec structure in your repository.

Frequently Asked Questions about openspec-workflow

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

FAQPage Schema
How do I manage OpenSpec artifacts for an AI agent workflow?

Managing OpenSpec artifacts for an AI agent workflow involves mapping stages to structured files. This skill enforces a repeatable workflow across eight stages, persisting questions, research, design, and specs into per-change folders.

What is the best way to structure OpenSpec change folders in a repository?

The best way to structure OpenSpec change folders is using a standard layout under openspec/changes/<change-id>/. This approach isolates artifacts for each change, enabling consistent downstream tooling and reliable audits.

How do I map QRSPI stages to OpenSpec proposal and spec files?

Mapping QRSPI stages to OpenSpec files requires defining stage-to-artifact relationships. The workflow maps the eight stages directly to canonical artifacts including questions, research, design, proposals, specs, slices, tasks, and archives.

Do I need to manually create templates for OpenSpec artifact management?

You do not need to manually create templates for OpenSpec artifact management. The workflow provides canonical artifact shapes and per-artifact templates, ensuring consistent formatting and adherence to change-archive rules.

Can I bootstrap the OpenSpec folder layout with a CLI command?

You can bootstrap the OpenSpec folder layout by running the /qrspi:init command. This initializes the required openspec directory structure in your repository, preparing it for subsequent artifact mapping across stages.

When should I use an OpenSpec-backed workflow for artifact management?

You should use an OpenSpec-backed workflow for artifact management when you need to persist, map, and audit changes across multiple stages. It suits projects requiring repeatable structures aligned with canonical templates and per-change folders.