change-implement

Automate technical change implementation by processing task checklists and enforcing architectural constraints.

Updated Jul 7, 2026

Search Tags:#automation #workflow #implementation #governance #spec-kit #task-management

Ready to run

npx skills add https://github.com/eavichay/mycli --skill change-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-implement
Source: https://github.com/eavichay/mycli/tree/main/.cursor/skills/change-implement
Command: npx skills add https://github.com/eavichay/mycli --skill change-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the implementation of technical changes defined in a spec-kit project, ensuring that tasks are executed in a consistent, governed, and verifiable manner.

Core Features & Use Cases

Hook-Driven Workflow: Automatically triggers pre- and post-execution hooks to ensure environment readiness and compliance.
Task Orchestration: Sequentially processes tasks defined in a change proposal, tracking completion status in real-time.
Use Case: When a developer needs to implement a new feature defined in a spec-kit change directory, this skill handles the loading of requirements, execution of tasks, and verification of project principles.

Quick Start

Use the change-implement skill to execute the tasks for the change proposal located in the changes/001-feature-implementation directory.

Frequently Asked Questions about change-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate task checklist execution for spec-kit change proposals?▼

Automate task checklist execution by sequentially processing change proposals, validating architectural constraints, and dispatching pre- and post-execution hooks to ensure governed compliance.

What is a hook-driven workflow for implementing technical changes?▼

A hook-driven workflow for implementing technical changes automatically triggers pre-execution validation for environment readiness and post-execution hooks to verify project principles upon completion.

Do I need a spec-kit compliant directory structure to enforce architectural constraints?▼

Yes, you need a spec-kit compliant directory structure with defined change specifications and extension hooks to enforce architectural constraints and manage the change proposal lifecycle properly.

How do I validate project principles before executing a change proposal?▼

Validate project principles before executing a change proposal by utilizing pre-execution hooks within the task orchestration workflow, which verify environment readiness and ensure architectural compliance before sequential task processing begins.

Can I track completion status in real-time during sequential task execution?▼

Yes, you can track completion status in real-time during sequential task execution as the workflow sequentially processes tasks defined in the change proposal and monitors progress throughout the implementation lifecycle.

What are the limitations of automating change implementation with task checklists?▼

Limitations of automating change implementation include strict dependency on a spec-kit compliant directory structure and defined extension hooks, meaning it cannot process tasks or enforce governance without these pre-existing project configurations.