Individual skill

openspec-feature-workflow

Use when a feature needs an OpenSpec change with proposal, design, specs, and tasks completed before coding. Trigger when the repo policy requires OpenSpec for non-trivial features, when the user asks for proposal/design/tasks first, or when behavior changes need durable change artifacts.

team-skills/openspec-feature-workflow/SKILL.md

Read pinned source

Source commit 1426ddcb85f203c7de8a13b5d1ba4cfd188fb265

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: Yes
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 201
Repository last updated: Jun 12, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category
design Derived category
operations Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 2,139 bytes
SKILL.mdcore · 1,845 bytes
agents/openai.yamlasset · 246 bytes
readme_cn.mddoc · 1,958 bytes
workflow.yamlasset · 489 bytes

Read excerpt


# OpenSpec Feature Workflow

## Overview

Use this skill for the OpenSpec half of feature delivery. It creates and completes the change artifacts needed before implementation.

This is an explicit opt-in workflow. Do not use it by default. Only use it when the user explicitly asks for this workflow, names this skill, or a repository policy explicitly requires it.

## Workflow

1. Derive or confirm a kebab-case change name.
2. Create the change under `openspec/changes/<change-name>/`.
3. Run `openspec status --change "<change-name>" --json` to inspect artifact order.
4. Read `openspec instructions <artifact> --change "<change-name>" --json` before writing each artifact.