skills.rest
ribeec20
ribeec20COMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-update

Manage requirement IDs, generate changelog entries, and ensure traceability in specification files.

Updated Feb 17, 2026
Search Tags:#changelog#documentation#version control#specification#requirements#traceability
One-click install
npx skills add https://github.com/ribeec20/vista-marketplace --skill spec-update-ribeec20
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-update
Source: https://github.com/ribeec20/vista-marketplace/tree/main/vista/skills/spec-update
Command: npx skills add https://github.com/ribeec20/vista-marketplace --skill spec-update-ribeec20

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that changes to specification files are meticulously tracked, maintaining a clear history of requirement modifications and their justifications.

Core Features & Use Cases

  • Requirement ID Management: Assigns and updates unique IDs for functional, non-functional, and business rule requirements.
  • Changelog Generation: Automatically appends changes to a changelog table within the spec file.
  • Traceability: Links requirement changes to Git commits and helps identify code impacted by spec updates.
  • Use Case: When a new edge case is discovered during feature implementation, use this Skill to add a new requirement ID, document the change in the spec's changelog, and ensure the commit message reflects the update.

Quick Start

Update the spec file for the 'my-feature' with changes related to the 'authentication' topic.

Frequently Asked Questions about spec-update

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

FAQPage Schema
How do I track specification changes and maintain traceability with my codebase?▼

You can track specification changes by managing unique requirement IDs, appending entries to a spec changelog, and searching your codebase for references to affected IDs to ensure bidirectional traceability.

What is the best way to manage requirement IDs for legacy specification files?▼

Managing requirement IDs for legacy files involves retroactively assigning unique identifiers to functional, non-functional, and business rule requirements so they can be tracked going forward.

How do I generate a changelog entry when modifying a requirement?▼

Generating a changelog entry is handled automatically by appending modification details directly into a changelog table within the specification file whenever a requirement is added, modified, or deprecated.

Does this specification update process integrate with Git commit conventions?▼

Yes, the specification update process integrates with Git by linking requirement changes to commits and ensuring commit messages accurately reflect the specification modifications.

Can I deprecate obsolete requirements without losing the specification history?▼

You can deprecate obsolete requirements while preserving history, because the process logs the deprecation in the changelog table and maintains the traceability links to past code references.

When do I need to update a specification file during feature implementation?▼

You need to update a specification file when a new edge case is discovered or when functional, non-functional, or business rules are modified, ensuring the changelog and Git commit reflect the update.

Related Skills

Explore More Software Engineering Skills→
0xdeafcafe0xdeafcafe

backfill-feature

Backfill retroactive ADRs, Gherkin specs, and characterization tests for existing software features.

Community
Advanced
Hopin-incHopin-inc
3

map-impact-analysis

Generate dependency graphs to forecast impacted files, domains, and tests from code changes.

Official
Advanced
codysumpter-cloudcodysumpter-cloud
2

chinese-commit-conventions

Enforce Chinese-friendly Conventional Commits format with commitlint integration.

Community
Basic
NagyViktNagyVikt
2

writing-plans

Generate test-driven implementation plans with granular engineering steps.

Community
Advanced