spec-update

Analyze git history to align spec documents with actual project state.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/srnnkls/tropos --skill spec-update-srnnkls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-update
Source: https://github.com/srnnkls/tropos/tree/main/skills/spec-update
Command: npx skills add https://github.com/srnnkls/tropos --skill spec-update-srnnkls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update spec documents to reflect the true state of work by analyzing git commits and working directory changes, reducing drift between planning and execution.

Core Features & Use Cases

  • Synchronizes specs with project reality by parsing commits, changes, and task evidence
  • Updates task status, content, and meta progress based on observed state
  • Applies to multi-spec workspaces and ongoing spec refinement

Quick Start

Run the /spec.update command against your target spec to sync its state with the latest commits.

Frequently Asked Questions about spec-update

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

FAQPage Schema
How do I update specs to reflect actual project state from git history?

To update specs from git history, you can run a command that parses commits and working directory changes, then aligns task status and content with observed evidence to reduce planning drift.

What is the best way to sync task status with recent git commits?

Syncing task status with git commits involves mapping commit evidence to tasks and updating state representations like tasks.yaml, ensuring your spec documents accurately reflect ongoing work.

How does parsing git commits align documentation with ongoing work?

Parsing git commits aligns documentation by analyzing the actual project state, mapping observed changes to planned tasks, and updating both task content and meta progress automatically.

Can I use this to update tasks.yaml across multi-spec workspaces?

Yes, you can apply this to multi-spec workspaces to update state representations like tasks.yaml, parsing commit evidence and mapping it to active specs folders for ongoing refinement.

Does spec synchronization work without manual status checks?

Spec synchronization works without manual checks by automatically analyzing git history and working directory changes to map evidence to tasks and update progress markers.

Why do my spec documents drift from actual code changes?

Spec documents drift from code changes when planning and execution diverge, requiring git history analysis to parse commits, map evidence to tasks, and update task status accordingly.