change-specify

Generate standardized spec.md, plan.md, and tasks.md files for change proposals.

Updated Jul 7, 2026

Search Tags:#git #workflow #planning #documentation #task management #specification

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent project documentation and fragmented task tracking by enforcing a structured, manifest-first approach to change management.

Core Features & Use Cases

Automated Specification: Generates standardized spec.md, plan.md, and tasks.md files based on user goals.
Lifecycle Management: Integrates with Git hooks to automate branch creation and feature tracking.
Use Case: When starting a new feature, use this skill to automatically scaffold the required documentation, risk register, and implementation checklist in the correct project directory.

Quick Start

Invoke the change-specify skill with a brief description of your desired feature to generate the full specification and task breakdown.

Frequently Asked Questions about change-specify

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

FAQPage Schema

How do I standardize technical change proposals and task planning in Git?▼

Standardize technical change proposals by generating consistent spec.md, plan.md, and tasks.md files. This enforces a structured, manifest-first approach to change management and integrates with Git hooks to automate branch creation and feature tracking.

What is a manifest-first approach to project documentation?▼

A manifest-first approach to project documentation solves inconsistent tracking by enforcing a structured lifecycle. It automatically scaffolds required risk registers, implementation checklists, and governance principles into a compliant directory before development begins.

How do I scaffold spec.md, plan.md, and tasks.md files for a new feature?▼

Scaffold spec.md, plan.md, and tasks.md files by invoking the skill with a brief description of your desired feature. It automatically generates the full specification, risk register, and task breakdown in the correct project directory.

Do I need a specific directory structure to manage feature specifications?▼

You need a project structure compliant with the .specify directory convention to manage lifecycle artifacts. This specific directory setup is required to facilitate consistent documentation and automated file generation for feature tracking.

Can I automate Git branch creation from a change proposal?▼

Automate Git branch creation from a change proposal through integrated Git hooks. The lifecycle management feature facilitates automated branch creation and feature tracking directly based on your standardized specification documents.

Why use standardized documentation for task breakdowns?▼

Use standardized documentation for task breakdowns to solve the problem of fragmented task tracking. Consistent implementation plans and checklists ensure coherent project documentation and align task execution with governance principles.