spec-update

Consolidate module specs, ADRs, and checkpoints after verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/overthestream/agent-dotfile --skill spec-update-overthestream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-update
Source: https://github.com/overthestream/agent-dotfile/tree/main/claude/skills/spec-update
Command: npx skills add https://github.com/overthestream/agent-dotfile --skill spec-update-overthestream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates and synchronizes formal specifications and supporting documentation after code implementation and verification are complete, ensuring consistency across modules, decisions, and checkpoints.

Core Features & Use Cases

  • Generate or update module specifications under docs/modules/{module}/README.md.
  • Create and merge ADRs under docs/decisions and consolidate checkpoint progress.
  • Produce a final completion summary and remove used checkpoints to keep docs clean.

Quick Start

Run the spec-update workflow after a successful verify to consolidate checkpoints into module specifications and ADRs, updating the published documentation.

Frequently Asked Questions about spec-update

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

FAQPage Schema
How do I consolidate specifications and ADRs after implementation?

To consolidate specifications and ADRs, run the spec-update workflow after successful verification to merge module specs, create ADRs, and remove completed checkpoints.

What is the best way to automate documentation updates after code verification?

Automating documentation updates involves applying a post-verification workflow that merges checkpoint progress into module specifications and generates corresponding ADRs under docs/decisions.

How do I clean up completed checkpoints in my documentation?

Cleaning up completed checkpoints requires consolidating their progress into final module specs and ADRs, which allows the workflow to safely delete the used checkpoints and keep docs clean.

When should I run a workflow to synchronize formal specifications?

You should synchronize formal specifications immediately after code implementation and verification are complete, ensuring consistency across module specs, decisions, and checkpoints before publishing.

Does spec-update work with existing module specifications under docs/modules?

Yes, the workflow targets existing documentation structures by updating or generating module specifications under docs/modules/{module}/README.md and merging ADRs under docs/decisions.