spec-auto-updater

Update specifications with approved changes and log rationale.

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/hohai99/antigravity-skills --skill spec-auto-updater
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-auto-updater
Source: https://github.com/hohai99/antigravity-skills/tree/main/.agent/skills/spec-auto-updater
Command: npx skills add https://github.com/hohai99/antigravity-skills --skill spec-auto-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps specifications in sync with the actual approved implementation, preventing dead documentation and misaligned behavior.

Core Features & Use Cases

  • Traceability and Change History: automatically updates the spec with approved changes and logs the rationale.
  • Downstream Impact Awareness: flags tests, documentation, and artifact updates needed after a spec change.
  • Use Case: After a change proposal is approved, run this skill to align the spec with the new behavior and update the Change Log.

Quick Start

After approving a spec change, run this skill to update the official specification and propagate changes to downstream docs.

Frequently Asked Questions about spec-auto-updater

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

FAQPage Schema
How do I update specifications to match approved implementation changes?

To update specifications for approved implementations, run this skill after a change proposal is approved. It aligns the official spec with the new behavior and logs the rationale to preserve traceability.

What is the best way to fix spec drift in a development project?

Remediating spec drift requires aligning specifications with the actual approved implementation state. This skill targets post-approval updates to enforce traceability and prevent misaligned behavior across development projects.

How do I track change history and rationale after modifying a specification?

Tracking change history after a spec modification is handled automatically by updating the specification with approved changes and logging the rationale in the Change Log to maintain governance.

Does updating a specification automatically flag downstream documentation impacts?

Updating a specification does flag downstream documentation impacts. The process signals required updates for tests, documentation, and artifacts needed after a spec change is applied.

When do I need to run a specification update workflow for governance and traceability?

You need to run a specification update workflow when a change proposal is approved and you must align the spec with new behavior. This enforces governance, preserves change history, and signals downstream impacts.