Agent Skills › bacoco/BMad-Skills › openspec-change-implementation

openspec-change-implementation

GitHub

根据已批准的 OpenSpec L0-1 提案，执行代码或配置变更。通过迭代实现、运行测试验证并记录执行日志，确保透明交付。若发现范围扩大或复杂性增加，则升级至 BMAD 流程。

.claude/skills/openspec-change-implementation/SKILL.md bacoco/BMad-Skills

Trigger Scenarios

用户说 'Implement this change' 或 'Apply the fix' 用户要求 'Execute proposal' 或应用 Bug 修复存在已批准且范围未超出的 OpenSpec 提案

Install

npx skills add bacoco/BMad-Skills --skill openspec-change-implementation -g -y

More Options

Non-standard path

npx skills add https://github.com/bacoco/BMad-Skills/tree/main/.claude/skills/openspec-change-implementation -g -y

Use without installing

npx skills use bacoco/BMad-Skills@openspec-change-implementation

指定 Agent (Claude Code)

npx skills add bacoco/BMad-Skills --skill openspec-change-implementation -a claude-code -g -y

安装 repo 全部 skill

npx skills add bacoco/BMad-Skills --all -g -y

预览 repo 内 skill

npx skills add bacoco/BMad-Skills --list

SKILL.md

Frontmatter

{
    "name": "openspec-change-implementation",
    "metadata": {
        "outputs": [
            "implemented-code",
            "execution-log",
            "test-results"
        ],
        "triggers": {
            "keywords": [
                "apply",
                "execute",
                "implement",
                "fix",
                "proposal"
            ],
            "patterns": [
                "apply this change",
                "implement the fix",
                "execute proposal",
                "apply the bug fix",
                "implement it"
            ]
        },
        "auto-invoke": true,
        "capabilities": [
            "change-implementation",
            "code-execution",
            "test-execution",
            "logging"
        ],
        "prerequisites": [
            "proposal"
        ]
    },
    "description": "Implements L0-1 changes from proposals.",
    "allowed-tools": [
        "Read",
        "Write",
        "Grep",
        "Bash"
    ]
}

OpenSpec Implement Skill

When to Invoke

Automatically activate when user:

Says "Implement this change", "Apply the fix", "Execute proposal"
Asks "Apply this bug fix", "Implement the proposal", "Execute the change"
Has an approved OpenSpec proposal ready to implement
Mentions "implement", "apply", "execute" with Level 0-1 context
Uses words like: apply, execute, implement, change, fix, proposal

Specific trigger phrases:

"Implement this change"
"Apply the bug fix"
"Execute the proposal"
"Apply this change: [proposal-id]"
"Implement proposal [X]"
"Execute the fix"

Prerequisites:

OpenSpec proposal exists and is approved
Change is still Level 0-1 (hasn't grown in scope)
Environment and dependencies are clear

Do NOT invoke when:

No proposal exists (use openspec-change-proposal first)
Scope has grown beyond Level 1 (escalate to BMAD)
Implementing a BMAD story (use bmad-development-execution instead)

Auto-escalate to BMAD when:

Implementation reveals hidden complexity
Scope expands beyond original proposal
Tests fail repeatedly indicating design issues

Mission

Apply small code or configuration changes approved via OpenSpec proposals, ensuring each task is executed transparently with testing evidence.

Inputs Required

proposal: latest proposal.md with decision history
tasks: tasks.md with sequenced work items and owners
environment: information about repositories, branches, and tooling needed for execution

Outputs

Code or configuration changes committed according to tasks
Test results demonstrating acceptance criteria were met
Updated proposal/tasks capturing status and follow-ups
execution-log.md documenting commands and evidence (template: assets/execution-log-template.md.template)

scripts/update_execution_log.py appends timestamped entries to the execution log inside openspec/changes/<change-id>/.

Process

Confirm scope and prerequisites via CHECKLIST.md.
Plan work referencing affected files and dependencies.
Implement tasks iteratively, documenting commands and results in execution-log.md via the script or manual edits.
Run relevant tests or validation steps after each change and capture evidence in the log.
Update artifacts and communicate completion or blockers.

Quality Gates

All checklist items must pass. If complexity grows beyond Level 1, escalate back to BMAD pathways.

Error Handling

When prerequisites or environment setup are missing, stop and request clarity.
If tests fail or scope expands, log findings and recommend next actions, including potential migration to BMAD development-execution.