openspec-bridge-propose

仓库创建 2026年7月28日最近提交 7 小时前SkillHot 收录 1 小时前

▸ 精选理由

阻止不完整或不合规的提案推进到讨论/计划阶段。

这个 Skill 做什么

包装并验证 OpenSpec 的提案，确保 GSD 阶段前链接变更完整。

在发起 GSD 阶段前，把要改动的提案、规格、设计和任务打包并验一次合不完整。它不是重写 OpenSpec 的产物生成功能，而是封装并调用 OpenSpec（比如 /opsx:propose）然后校验结果，避免出现两个互相冲突的规格系统。遇到没有关联变更就要继续推进讨论或计划时用它，能保证链接和产物齐全再进入下一步。

▸ 展开 SKILL.md 英文原文

Ensures a GSD phase has a valid, complete OpenSpec change (proposal+specs+design+tasks) before /gsd-discuss-phase or /gsd-plan-phase will proceed. Wraps native /opsx:propose (or /opsx:ff for the expanded profile) and validates the result, rather than reimplementing artifact generation.

开发编程提案验证OpenSpec集成规范一致性通用

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/mshegolev/gsd-openspec-integration/main/capabilities/openspec/skills/openspec-bridge-propose/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/mshegolev/gsd-openspec-integration/main/capabilities/openspec/skills/openspec-bridge-propose/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

## Purpose

This is the skill `discuss:pre` tells the user to run when no change is linked. It is a validating wrapper around OpenSpec's own proposal-generation skills — never a reimplementation of them — because duplicating that logic would create exactly the "two competing spec systems" this integration exists to avoid.

## Invocation conditions

- User runs it directly (or is told to by the `discuss:pre` fragment).
- Called with a change-id and a one-sentence description of the change.

## Required inputs

- `change-id` (kebab-case, matches OpenSpec's own naming convention)
- A one-sentence description of intent — passed straight to `/opsx:propose`.
- Optionally, the GSD phase number this

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有