speckit-workflows-issue-sync-before-specify

Sync linked GitHub issue status before the before_specify hook.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps issue status in sync automatically for before_specify workflows, reducing manual updates and inconsistencies in Speckit automation.

Core Features & Use Cases

  • Ensure linked GitHub issue status is reflected in spec-kit workflows prior to hook execution.
  • Supports standard .specify project structures; works with common issue lifecycle events.
  • Improves traceability by keeping automation context aligned with issue state.

Quick Start

Execute the provided script to sync the linked issue status before the before_specify hook.

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

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

FAQPage Schema
How do I sync GitHub issue status before running spec-kit workflows?▼

You can sync GitHub issue status before the before_specify hook by executing the provided script under the scripts/ directory, which aligns linked issue states with spec-kit workflows.

Why does my spec-kit automation context mismatch with linked GitHub issues?▼

Spec-kit automation context mismatches occur when linked GitHub issue statuses are not updated before hook execution, which this sync script resolves by standardizing issue states beforehand.

Do I need a .specify directory to sync GitHub issues before the specify hook?▼

Yes, you need a .specify directory because this sync script is designed for spec-kit project structures that organize workflows and trigger automation context within that specific directory layout.

What format does the spec-kit sync script require for SKILL.md?▼

The spec-kit sync script requires a SKILL.md file containing frontmatter with a name and description, alongside an executable script located under the scripts/ directory to perform the synchronization.

Can I use this issue sync workflow without GitHub dependencies?▼

No, this workflow specifically syncs the status of linked GitHub issues, requiring GitHub integration to pull issue state updates and maintain traceability within spec-kit automation workflows.