speckit-workflows-issue-sync-before-tasks

Sync linked GitHub issue status before the before_tasks hook executes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

When using Speckit workflows, linked GitHub issues can fall out of date as tasks progress. This skill automates syncing the issue status before the before_tasks hook runs, ensuring alignment between task progress and issue state.

Core Features & Use Cases

  • Automatically updates the status of a linked issue as part of the workflow before tasks execute.
  • Maintains consistency between tasks in the Speckit extension and corresponding GitHub issues across common CI scenarios.
  • Use Case: before a build starts, the linked issue is set to "in progress" so stakeholders see real-time progress.

Quick Start

Run the update-linked-issue script to align the linked GitHub issue status before the before_tasks hook executes.

Frequently Asked Questions about speckit-workflows-issue-sync-before-tasks

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

FAQPage Schema
How do I sync a linked GitHub issue status before a build starts?

To sync a linked GitHub issue status before a build, automate the update process using the before_tasks hook. This ensures the issue state reflects real-time progress before subsequent workflow tasks execute.

What is the before_tasks hook used for in Speckit workflow extensions?

The before_tasks hook in Speckit workflow extensions triggers automated scripts, such as updating linked GitHub issue statuses, ensuring alignment between task progress and issue state before main workflow execution.

Do I need a specific project structure to automate GitHub issue syncing?

Yes, automating GitHub issue syncing requires a compatible spec-kit project structure. The workflow relies on executing the Bash script located at .specify/extensions/workflows/scripts/bash/update-linked-issue.sh.

Why do linked GitHub issues fall out of date during Speckit workflows?

Linked GitHub issues fall out of date during Speckit workflows because task progress occurs independently of issue tracking. Automating status sync before the before_tasks hook prevents this misalignment.

Can I update GitHub issue state automatically in CI scenarios?

Yes, you can automatically update GitHub issue state in CI scenarios. The update-linked-issue Bash script integrates into workflow extensions to set linked issues to in-progress before tasks run.

What are the limitations of using Bash scripts for GitHub issue synchronization?

Bash script limitations for GitHub issue synchronization include strict dependency on a compatible spec-kit project structure and specific file paths within the .specify/extensions directory for proper execution.