spec-update

Guide agents through creating, implementing, and reviewing spec update documents.

140|20|Updated Jan 8, 2026

Search Tags:#workflow #planning #versioning #collaboration #spec-update #update-management

Ready to run

npx skills add https://github.com/HHU3637kr/skills --skill spec-update-hhu3637kr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-update
Source: https://github.com/HHU3637kr/skills/tree/main/spec-update
Command: npx skills add https://github.com/HHU3637kr/skills --skill spec-update-hhu3637kr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates end-to-end spec update cycles by guiding an agent through creating, implementing, and reviewing update documents.

Core Features & Use Cases

In-place updates: Keeps all update work in the original feature directory, avoiding new folders.
Incremental numbering: Enforces update-xxx.md sequencing (update-001, update-002, etc.) to track changes over time.
Collaborative workflow: Supports single-agent execution or multi-role review for larger updates.

Quick Start

Create update-001.md in the same directory as plan.md and begin the end-to-end update workflow.

Frequently Asked Questions about spec-update

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

FAQPage Schema

How do I automate spec updates when feature requirements change in an existing directory?▼

To automate spec updates, this Skill guides an agent through creating, implementing, and reviewing update documents. It preserves all in-place updates in the original feature directory, enforcing incremental update-xxx.md numbering to track changes over time without creating new folders.

Do I need existing plan.md and summary.md files to start the update workflow?▼

Yes, existing plan.md and summary.md files are strict prerequisites to start the update workflow. The Skill requires these documents to exist in the same directory as the newly created update-001.md file to properly guide the end-to-end feature update cycle.

What is the best way to manage incremental versioning for feature specification changes?▼

The best way to manage incremental versioning is through enforced update-xxx.md sequencing. This Skill automatically guides agents to create update-001, update-002, and subsequent files, preserving previous versions in place to maintain a clear historical track of specification changes.

Can I use a single agent for large feature updates or is multi-role collaboration required?▼

You can use a single agent for standard execution or enable multi-role collaboration for larger updates. The Skill supports both workflows, allowing flexible management of the end-to-end update cycle depending on the complexity and scale of your feature changes.

How to create an update document for changing feature designs without losing original plans?▼

To create an update document without losing original plans, generate an update-001.md file in the same directory as your plan.md. The Skill enforces in-place updates, ensuring original specifications are preserved while guiding the agent through implementing and reviewing the new changes.