speckit-issuesync.after-specify

Sync linked issue statuses after the after_specify hook in speckit workflows.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-issuesync-after-specify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-issuesync.after-specify
Source: https://github.com/pradeepmouli/lspeasy/tree/main/.github/skills/speckit-issuesync.after-specify
Command: npx skills add https://github.com/pradeepmouli/lspeasy --skill speckit-issuesync-after-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync linked issue statuses after the after_specify hook in speckit workflows, preventing drift between specifications and linked issues.

Core Features & Use Cases

  • Syncs issue status after the after_specify hook within speckit workflows.
  • Works within .specify/extensions/workflows to keep issue tracking aligned with spec state.
  • Useful for automation, auditing, and CI of specification-driven projects.

Quick Start

Run the update-linked-issue script with the after_specify event to synchronize statuses.

Frequently Asked Questions about speckit-issuesync.after-specify

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

FAQPage Schema
How do I sync linked GitHub issue status after the after_specify hook in speckit?

To sync linked GitHub issue status after the after_specify hook, run the update-linked-issue.sh script within your .specify/extensions/workflows. This automatically aligns issue tracking with your current spec state.

What does after_specify hook automation do for speckit workflows?

The after_specify hook automation prevents status drift between specifications and linked GitHub issues. It triggers a script to read and update issue tracking, ensuring issue state matches the latest spec workflow changes.

Do I need a configured GitHub repository to sync speckit issue statuses?

Yes, you need a configured GitHub repository to read and update issues. The sync requires the update-linked-issue.sh script and an active GitHub connection to apply status updates from speckit workflows.

When should I use after_specify linked issue synchronization in spec-kit projects?

Use after_specify linked issue synchronization for automation, auditing, and CI in spec-kit projects. It is necessary when your workflow defines .specify/extensions and you need to keep issue tracking aligned with specification state.

Why are linked GitHub issues drifting from my speckit specification state?

Linked GitHub issues drift from speckit specification state when statuses are not synced after workflow updates. Running the update-linked-issue.sh script on the after_specify event prevents this by aligning issue tracking automatically.