Check for Spec-Kit Updates

You are checking whether the upstream github/spec-kit repository has been updated since this plugin's templates were last synchronized. This helps you stay current with the latest Spec-Driven Development methodology.

How This Works

This plugin's skills were derived from the spec-kit repository (commit 94ba857b78074024f095b08b45802e17d2bff653). The upstream repository evolves — templates improve, new commands are added, and the methodology is refined.

The sync mechanism stores metadata in .speckit/upstream.json to track when you last checked for updates.

Workflow

Step 1: Check Local Metadata

Read .speckit/upstream.json if it exists:

{
  "source": "github.com/github/spec-kit",
  "source_sha": "[last known upstream commit SHA]",
  "last_synced": "[date]",
  "plugin_version": "[plugin version]"
}

If the file doesn't exist, report: "No sync metadata found. Run /spec-kit:init to initialize sync tracking."

Step 2: Fetch Upstream Status

Check the upstream repository for recent changes. Use one of these methods (in order of preference):

Method 1: Via GitHub API (if internet access is available)

Fetch the latest commit info from the upstream repository:

• URL: https://api.github.com/repos/github/spec-kit/commits/main
• Also fetch releases: https://api.github.com/repos/github/spec-kit/releases/latest

Parse the response to get:

• Latest commit SHA
• Latest commit date
• Latest release tag and date

Method 2: Via git (if upstream is reachable)

git ls-remote https://github.com/github/spec-kit.git HEAD

Method 3: Offline (if no internet access) Report that internet access is needed to check for updates and provide manual check instructions.

Step 3: Compare Versions

Compare the current state with the stored metadata:

Spec-Kit Update Status
======================
Plugin version:        [current version]
Last synced:           [date from upstream.json, or "never"]
Known upstream SHA:    [SHA from upstream.json]
Current upstream SHA:  [SHA from GitHub API]
Latest release:        [version tag from GitHub API]

Determine the update status:

• Up to date: Current SHA matches known SHA
• Updates available: Upstream SHA differs from known SHA
• Check failed: Could not reach GitHub API

Step 4: Report Changes (if updates available)

If updates are available, provide a summary of what changed. Check the CHANGELOG or commit messages from the upstream repository:

• URL: https://api.github.com/repos/github/spec-kit/commits?since=[last_synced_date]&per_page=20

Group changes by category:

• 🆕 New commands/templates: New files added to templates/commands/
• 📝 Template updates: Changes to existing templates
• 🔧 Methodology changes: Changes to workflows or instructions
• 🐛 Bug fixes: Corrections to templates or workflows

Format the report:

Updates Available in github/spec-kit
=====================================
Time since last sync: [N days/weeks]
Commits since sync:   [N]

Notable Changes:
  🆕 [new command or template]
  📝 [updated template]
  🔧 [methodology change]

Changed Files:
  templates/commands/specify.md     — updated
  templates/commands/plan.md        — updated
  templates/spec-template.md        — updated

For full details: https://github.com/github/spec-kit/commits/main

Step 5: Provide Update Instructions

Based on what changed, provide specific update guidance:

If new commands were added (e.g., a new templates/commands/xyz.md appeared):

Action: New skill available
  The upstream spec-kit has a new command: [command name]
  
  To add this skill to your local plugin, contact your plugin maintainer
  or follow the migration guide at:
  https://github.com/github/spec-kit/blob/main/docs/upgrade.md

  Plugin source: [path to plugin directory]

If existing templates were updated:

Action: Template updates available
  Your local skills may have outdated methodology. Key changes:
  
  [List specific changes]
  
  Option 1: Update this project's templates
    The .speckit/ templates can be refreshed by running /spec-kit:init
    (Note: this only updates the .speckit/ templates, not the plugin skills)
  
  Option 2: Update the plugin skills
    Contact your plugin maintainer to get updated SKILL.md files,
    or update them manually from:
    https://github.com/github/spec-kit/tree/main/templates/commands

If no changes:

✅ Your spec-kit plugin is up to date!
   Last checked: [today's date]
   Upstream SHA: [SHA]

Step 6: Update Sync Metadata

Update .speckit/upstream.json with today's check date:

{
  "source": "github.com/github/spec-kit",
  "source_sha": "[latest SHA or existing SHA if check failed]",
  "last_synced": "[today's date]",
  "last_checked": "[today's date]",
  "plugin_version": "2.0.0"
}

If upstream SHA changed and user acknowledged the update, update source_sha to the new value.

Manual Update Process

If you want to manually sync with the latest upstream:

1. For project templates (.speckit/ directory):

   • Run /spec-kit:init to regenerate templates from the built-in skill definitions
   • This updates .speckit/*.md templates to match the current skill version

2. For skill methodology (the SKILL.md files in the plugin):

   • View the latest command templates at: https://github.com/github/spec-kit/tree/main/templates/commands
   • Compare with your local skills in the plugin's skills/ directory
   • Update the relevant SKILL.md files with the new methodology

3. For completely fresh sync:

   • Check the plugin's source repository for updated skill files
   • The plugin skills were last synced from commit 94ba857b78074024f095b08b45802e17d2bff653

Upstream Repository Information

Field	Value
Repository	https://github.com/github/spec-kit
Commands reference	https://github.com/github/spec-kit/tree/main/templates/commands
Changelog	https://github.com/github/spec-kit/blob/main/CHANGELOG.md
Releases	https://github.com/github/spec-kit/releases
Upgrade guide	https://github.com/github/spec-kit/blob/main/docs/upgrade.md