change-specify

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.

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.

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.

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.

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.

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.