openspec-ff-change
A tool to quickly scaffold and create necessary project deliverables based on defined specs.
Install
mkdir -p .claude/skills/openspec-ff-change && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1097" && unzip -o skill.zip -d .claude/skills/openspec-ff-change && rm skill.zipInstalls to .claude/skills/openspec-ff-change
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
快速创建实现所需的所有产出物。当用户想要快速创建实现所需的所有产出物，而不是逐个创建时使用。Key capabilities
- →Scaffold a new change directory
- →Get artifact build order
- →Create artifacts based on instructions
- →Track artifact progress
- →Display final status of created artifacts
How it works
The skill uses the openspec CLI to scaffold a change directory, determine the build order of required artifacts, and then iteratively creates each artifact by following specific instructions and templates.
Inputs & outputs
When to use openspec-ff-change
- →Scaffold a new implementation change
- →Create project artifacts based on specs
- →Track progress of development tasks
- →Generate boilerplate documentation
About this skill
快速完成产出物创建 - 一次性生成开始实现所需的一切。
输入：用户的请求应包含变更名称（kebab-case）或对他们想要构建内容的描述。
步骤
-
如果没有提供明确的输入，询问他们想要构建什么
使用 AskUserQuestion tool（开放式，无预设选项）询问：
"您想要处理什么变更？请描述您想要构建或修复的内容。"
根据他们的描述，推导出一个 kebab-case 名称（例如："add user authentication" →
add-user-auth）。重要提示：在不了解用户想要构建什么的情况下，请勿继续。
-
创建变更目录
openspec-cn new change "<name>"这将在
openspec/changes/<name>/创建一个脚手架变更。 -
获取产出物构建顺序
openspec-cn status --change "<name>" --json解析 JSON 以获取：
applyRequires: 实现前所需的产出物 ID 数组（例如：["tasks"]）artifacts: 所有产出物及其状态和依赖项的列表
-
按顺序创建产出物直到准备好应用
使用 TodoWrite tool 跟踪产出物的进度。
按依赖顺序循环遍历产出物（没有待处理依赖项的产出物优先）：
a. 对于每个
ready（依赖项已满足）的产出物：- 获取指令：
openspec-cn instructions <artifact-id> --change "<name>" --json - 指令 JSON 包括：
context：项目背景（对你的约束 - 不要包含在输出中）rules：产出物特定规则（对你的约束 - 不要包含在输出中）template：用于输出文件的结构instruction：此产出物类型的模式特定指导outputPath：写入产出物的位置dependencies：已完成的产出物，用于读取上下文
- 读取任何已完成的依赖文件以获取上下文
- 使用
template作为结构创建产出物文件 - 应用
context和rules作为约束 - 但不要将它们复制到文件中 - 显示简短进度："✓ 已创建 <artifact-id>"
b. 继续直到所有
applyRequires产出物完成- 创建每个产出物后，重新运行
openspec-cn status --change "<name>" --json - 检查
applyRequires中的每个产出物 ID 在 artifacts 数组中是否具有status: "done" - 当所有
applyRequires产出物完成时停止
c. 如果产出物需要用户输入（上下文不清楚）：
- 使用 AskUserQuestion tool 进行澄清
- 然后继续创建
- 获取指令：
-
显示最终状态
openspec-cn status --change "<name>"
输出
完成所有产出物后，总结：
- 变更名称和位置
- 已创建产出物的列表及简要描述
- 准备就绪："所有产出物已创建！准备好实现。"
- 提示："运行
/opsx:apply或要求我实现以开始处理任务。"
产出物创建指南
- 遵循每个产出物类型的
openspec-cn instructions中的instruction字段 - 模式定义了每个产出物应包含的内容 - 遵循它
- 在创建新产出物之前阅读依赖产出物以获取上下文
- 使用
template作为输出文件的结构 - 填充其各个部分 - 重要提示：
context和rules是对你的约束，而不是文件内容- 不要将
<context>、<rules>、<project_context>块复制到产出物中 - 这些引导你编写内容，但不应出现在输出中
- 不要将
护栏
- 创建实现所需的所有产出物（由 Schema 的
apply.requires定义） - 在创建新产出物之前始终阅读依赖产出物
- 如果上下文极其不清楚，询问用户 - 但倾向于做出合理的决定以保持势头
- 如果同名变更已存在，建议继续处理该变更
- 在继续下一个之前，验证写入后每个产出物文件是否存在
Prerequisites
Limitations
- →Requires a clear user request for what to build
- →Cannot proceed without knowing what the user wants to build
How it compares
This skill automates the creation of all required project artifacts at once, rather than creating them individually.
Compared to similar skills
openspec-ff-change side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| openspec-ff-change (this skill) | 3 | 6mo | Review | Beginner |
| linear | 10 | 2mo | No flags | Beginner |
| zapier-workflows | 11 | 8mo | Review | Beginner |
| attio-skill-generator | 7 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by studyzy
View all by studyzy →You might also like
linear
lobehub
Linear issue management guide. Use when working with Linear issues, creating issues, updating status, or adding comments. Triggers on Linear issue references (LOBE-xxx), issue tracking, or project management tasks. Requires Linear MCP tools to be available.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
attio-skill-generator
kesslerio
Generate use-case-specific Attio workflow skills from templates. Use when creating new skills for lead qualification, deal management, customer onboarding, or custom Attio workflows.
automation-brainstorm
MacroMan5
Interactive workflow design advisor for Power Automate, n8n, Make, Zapier and other platforms. Guides users through planning automation workflows with smart questions about triggers, actions, data flow, and error handling. Uses research sub-agent to find best practices and generates detailed implementation plan. Triggers when user mentions "create workflow", "build flow", "design automation", "need ideas for", or describes workflow requirements without having a complete design.
daily-briefing
anthropics
Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".
jira
davila7
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.