SkillsAdd

smithery/bacoco

openspec-change-implementation

Implements L0-1 changes from proposals.

Installation

$ npx skills add smithery/bacoco --skill openspec-change-implementation
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

prisma-driver-adapter-implementation Similar name
prisma/skills

Required reference for Prisma ORM 7 SQL driver adapter work.

258.3K installs
create-implementation-plan Similar name
github/awesome-copilot

Create a new implementation plan file for new features, refactoring existing code or upgrading …

12.5K installs
update-implementation-plan Similar name
github/awesome-copilot

Update an existing implementation plan file with new or update requirements to provide new feat…

11.1K installs
create-github-issues-feature-from-implementation-plan Similar name
github/awesome-copilot

Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request…

9.3K installs
breakdown-feature-implementation Similar name
github/awesome-copilot

Prompt for creating detailed feature implementation plans, following Epoch monorepo structure.

9.3K installs
notion-spec-to-implementation Similar name
openai/skills

Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementin…

2.5K installs

Also in this package

Other skills from smithery/bacoco · top by installs.

npx skills add smithery/bacoco
synapse 0 openspec-change-proposal 0 openspec-change-closure 0 main-workflow-router 0 core-skill-creation 0 bmad-ux-design 0 bmad-test-strategy 0 bmad-taskmaster-mcp-bootstrap 0 bmad-story-planning 0 bmad-security-review 0

Browse all from smithery/bacoco

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Write, Grep, Bash
More metadata
auto-invoke
1
triggers
{"patterns":["apply this change","implement the fix","execute proposal","apply the bug fix","implement it"],"keywords":["apply","execute","implement","fix","proposal"]}
capabilities
["change-implementation","code-execution","test-execution","logging"]
prerequisites
["proposal"]
outputs
["implemented-code","execution-log","test-results"]

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,312 B
  • docs SUMMARY.md 77 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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/updateexecutionlog.py appends timestamped entries to the execution log inside openspec/changes/<change-id>/.

Process

  1. Confirm scope and prerequisites via CHECKLIST.md.
  2. Plan work referencing affected files and dependencies.
  3. Implement tasks iteratively, documenting commands and results in execution-log.md via the script or manual edits.
  4. Run relevant tests or validation steps after each change and capture evidence in the log.
  5. 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.