Issue Spec Propose
higress-group/higress
Create or continue proposal, SPEC, QUESTION, design, and TASK artifacts for an issue-spec change.
A skill your agent uses when a feature needs an OpenSpec change with proposal, design, specs, and tasks completed before coding.
MITAuto-check passed
Install Openspec Feature Workflow
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills openspec-feature-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/team-skills/openspec-feature-workflow .claude/skills/openspec-feature-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openspec-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/openspec-feature-workflow into .claude/skills/openspec-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-feature-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/openspec-feature-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills openspec-feature-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/team-skills/openspec-feature-workflow .agents/skills/openspec-feature-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openspec-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/openspec-feature-workflow into .agents/skills/openspec-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-feature-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills openspec-feature-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/team-skills/openspec-feature-workflow .cursor/skills/openspec-feature-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openspec-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/openspec-feature-workflow into .cursor/skills/openspec-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-feature-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git --path team-skills/openspec-feature-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills openspec-feature-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/team-skills/openspec-feature-workflow .gemini/skills/openspec-feature-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openspec-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/openspec-feature-workflow into .gemini/skills/openspec-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-feature-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills openspec-feature-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/team-skills/openspec-feature-workflow .github/skills/openspec-feature-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openspec-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/openspec-feature-workflow into .github/skills/openspec-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-feature-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SYZ-Coder/superpowers-openspec-team-skills openspec-feature-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SYZ-Coder/superpowers-openspec-team-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/team-skills/openspec-feature-workflow .opencode/skills/openspec-feature-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openspec-feature-workflow" agent skill from https://github.com/SYZ-Coder/superpowers-openspec-team-skills/tree/main/team-skills/openspec-feature-workflow into .opencode/skills/openspec-feature-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openspec-feature-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openspec-feature-workflow- GitHub stars
- 196
- Token cost
- ~462 tokens
- SKILL.md length
- 188 words
- Files
- 5
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a feature needs an OpenSpec change with proposal, design, specs, and tasks completed before coding.
- Works in 6 steps: Derive or confirm a kebab-case change… → Create the change under… → Run openspec status --change "" --json… → …
- A feature needs an OpenSpec change with proposal
- SKILL.md covers Overview, Workflow, When to Use and Artifact Expectations, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Openspec Feature Workflow is an agent skill from SYZ-Coder/superpowers-openspec-team-skills. 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.
Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `README.md`, `agents/openai.yaml` and `readme_cn.md`).
The repository describes itself as: 一套带有记忆和自学习的harness-team-skills企业级编程技能组合库 针对superpowers+openspec 进行按需组合使用,适用于个人与团队协作进行AI编程. The licence is MIT.
When your agent uses it
- A feature needs an OpenSpec change with proposal
- Tasks completed before coding
- The repo policy requires OpenSpec for non-trivial features
- The user asks for proposal/design/tasks first
Example prompts
- “/openspec-feature-workflow”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Derive or confirm a kebab-case change name.
- Create the change under openspec/changes//.
- Run openspec status --change "" --json to inspect artifact order.
- Read openspec instructions --change "" --json before writing each artifact.
- Complete artifacts in dependency order
- Re-check status until all apply-required artifacts are done before implementation starts.
What it can do on your machine
Read from SKILL.md and the folder at commit 1426ddc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Openspec Feature Workflow loads about 462 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 188 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from SYZ-Coder/superpowers-openspec-team-skills at commit 1426ddc, republished under its MIT licence (© SYZ-Coder). 188 words, ~462 tokens.
Download SKILL.mdSave it as
.claude/skills/openspec-feature-workflow/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- openspec-feature-workflow
- description
- 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.
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
- Derive or confirm a kebab-case change name.
- Create the change under
openspec/changes/<change-name>/. - Run
openspec status --change "<change-name>" --jsonto inspect artifact order. - Read
openspec instructions <artifact> --change "<change-name>" --jsonbefore writing each artifact. - Complete artifacts in dependency order:
proposal.mddesign.mdspecs/.../spec.mdtasks.md
- Re-check status until all apply-required artifacts are done before implementation starts.
When to Use
- The user explicitly asks for proposal/design/tasks before coding
- The user explicitly names
$openspec-feature-workflow AGENTS.mdor team policy explicitly requires this workflow
Artifact Expectations
proposal.md: why and what changeddesign.md: technical approach and trade-offsspecs/.../spec.md: normative requirements and scenariostasks.md: executable implementation checklist
Guardrails
- Do not skip dependency order from
openspec status - Do not copy instruction metadata into artifact files
- Do not start coding until required artifacts are ready
© SYZ-Coder, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files in team-skills/openspec-feature-workflow of SYZ-Coder/superpowers-openspec-team-skills.
- SKILL.md
- README.md
- agents/openai.yaml
- readme_cn.md
- workflow.yaml
Open the folder on GitHubat commit 1426ddc
Compare with similar skills
Openspec Feature Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openspec Feature Workflow this skillSYZ-Coder/superpowers-openspec-team-skills | 196 | — | ~462 | Automated safety check: Pass | MIT | |
| Issue Spec Proposehigress-group/higress | 9.5k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Spec Writergarrytan/gstack | 136k | — | ~14k | Automated safety check: Notes | MIT | |
| Openspec Sync Specstsedio/tsed | 3.1k | 6 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Geo Proposalsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| OpenSpec Bulk Change ArchiverFission-AI/OpenSpec | 71k | 2 repos | ~5.6k | Automated safety check: Pass | MIT |
Similar skills
Spec Writer
garrytan/gstack
Converts a vague idea into a precise, executable spec in five phases, files it as an issue and can start an agent on it in a fresh worktree.
Openspec Sync Specs
tsedio/tsed
Sync delta specs from an OpenSpec change to main specs. An agent skill from tsedio/tsed.
Geo Proposal
sickn33/agentic-awesome-skills
Auto-generate a professional, client-ready GEO service proposal from audit data.
OpenSpec Bulk Change Archiver
Fission-AI/OpenSpec
Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.
Better Proposals Automation
ComposioHQ/awesome-claude-skills
Automate Better Proposals tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
More from SYZ-Coder/superpowers-openspec-team-skills
Superpowers Openspec Superpowers Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when the user explicitly wants this workflow, wants Superpowers exploration before OpenSpec artifacts, or is confirming or continuing tasks that this workflow already…
Openspec Superpowers Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when the user explicitly wants an OpenSpec-first path that creates proposal, design, specs, and tasks before handing off to Superpowers execution, verification, and optional…
Superpowers Feature Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when feature work needs the Superpowers stages before or during implementation: brainstorming, design confirmation, implementation planning, worktree setup, test-driven…
Superpowers Learning Workflow
SYZ-Coder/superpowers-openspec-team-skills
A skill your agent uses when the user explicitly wants to capture lessons from completed work, persist durable project knowledge, or turn repeated patterns into reusable learning notes for future…
Questions about Openspec Feature Workflow
What does Openspec Feature Workflow do?
A skill your agent uses when a feature needs an OpenSpec change with proposal, design, specs, and tasks completed before coding. Openspec Feature Workflow is an agent skill from SYZ-Coder/superpowers-openspec-team-skills. Use when a feature needs an OpenSpec change with proposal, design, specs, and tasks completed before coding.
When should I use Openspec Feature Workflow?
Openspec Feature Workflow fits situations like: A feature needs an OpenSpec change with proposal; tasks completed before coding; the repo policy requires OpenSpec for non-trivial features; the user asks for proposal/design/tasks first.
How do I install Openspec Feature Workflow in Claude Code?
Run `npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a claude-code`. Or copy the skill folder (team-skills/openspec-feature-workflow in SYZ-Coder/superpowers-openspec-team-skills) into .claude/skills/openspec-feature-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Openspec Feature Workflow in Codex?
Run `npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a codex`. Or copy the skill folder (team-skills/openspec-feature-workflow in SYZ-Coder/superpowers-openspec-team-skills) into .agents/skills/openspec-feature-workflow in your project. Codex loads it when a task matches its description.
Can I use Openspec Feature Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SYZ-Coder/superpowers-openspec-team-skills --skill openspec-feature-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openspec-feature-workflow, .gemini/skills/openspec-feature-workflow, .github/skills/openspec-feature-workflow and .opencode/skills/openspec-feature-workflow in your project.
What does Openspec Feature Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Openspec Feature Workflow is instructions for the agent only.
Does Openspec Feature Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Openspec Feature Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Openspec Feature Workflow use?
Openspec Feature Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openspec Feature Workflow use?
About 462 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Openspec Feature Workflow?
Skills that share tags, products or a category with Openspec Feature Workflow: Issue Spec Propose (higress-group/higress, 9.5k stars), Spec Writer (garrytan/gstack, 136k stars), Openspec Sync Specs (tsedio/tsed, 3.1k stars) and Geo Proposal (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openspec Feature Workflow?
SYZ-Coder (a GitHub user) maintains it in SYZ-Coder/superpowers-openspec-team-skills, which has 196 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on June 12, 2026.
Source: SYZ-Coder/superpowers-openspec-team-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.