skills.rest
jmservera
jmserveraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

SpecKit → Squad Issue Handoff

Convert SpecKit tasks.md into labeled GitHub issues after Design Review.

1|Updated Mar 23, 2026
Search Tags:#workflow#handoff#speckit#issue-tracking#design-review#squad
One-click install
npx skills add https://github.com/jmservera/squad-speckit-bridge --skill speckit-squad-issue-handoff
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: SpecKit → Squad Issue Handoff
Source: https://github.com/jmservera/squad-speckit-bridge/tree/main/.squad/skills/speckit-squad-handoff
Command: npx skills add https://github.com/jmservera/squad-speckit-bridge --skill speckit-squad-issue-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The handoff between SpecKit planning and Squad execution can be error-prone and slow when done manually. This Skill automates the boundary by ensuring SpecKit-produced tasks.md outputs are handed off to Squad for issue creation only after a Design Review ceremony, preserving context and routing information.

Core Features & Use Cases

  • Enforces the handoff boundary: SpecKit plans, Squad creates issues with the squad label and routing metadata.
  • Preserves traceability: original task IDs are retained in issue titles and a reference to the source tasks.md is included.
  • Supports end-to-end workflows: integrates planning, triage, execution, and knowledge feedback into SpecKit.
  • Encourages proper ceremony: ensures Design Review before issues are created, capturing contextual learnings for future cycles.

Quick Start

Run SpecKit specify → plan → tasks to generate tasks.md, then trigger the bridge to transform each task into a Squad issue after Design Review.

Frequently Asked Questions about SpecKit → Squad Issue Handoff

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

FAQPage Schema
How do I convert SpecKit tasks.md into GitHub issues for Squad execution?▼

The handoff bridge converts SpecKit tasks.md into GitHub issues by standardizing the transformation after a Design Review ceremony, ensuring each issue includes the squad label and preserves original task IDs for end-to-end traceability.

Why does the SpecKit to Squad handoff require a Design Review before issue creation?▼

A Design Review is required before issue creation to enforce the handoff boundary between SpecKit planning and Squad execution, capturing contextual learnings for future cycles and ensuring proper routing metadata.

How are original task IDs preserved when handing off tasks.md to issue tracking?▼

Original task IDs are preserved by retaining them in the GitHub issue titles during the handoff process, while each issue also includes a reference to the source tasks.md file to maintain end-to-end traceability.

Can I bulk assign GitHub issues during the SpecKit to Squad handoff process?▼

No, bulk assignments are explicitly avoided during the SpecKit to Squad handoff. The workflow enforces proper triage and issue creation individually to ensure accurate routing metadata and end-to-end traceability.

What is the best way to maintain traceability between SpecKit planning and Squad execution?▼

The best way to maintain traceability is to standardize the handoff boundary so each GitHub issue includes the squad label, preserves the original task ID in the title, and references the source tasks.md file.

Related Skills

Explore More Software Engineering Skills→
StrangeDaysTechStrangeDaysTech
2

speckit-implement

Execute Speckit implementation plans with checklist gates and extension hooks.

Official
Advanced
jmserverajmservera
1

speckit-bridge

Inject Squad memory into Spec Kit planning cycles and design reviews.

Community
Advanced
redpanda-dataredpanda-data
34

triage

Automate issue categorization, labeling, and comments on GitHub and Jira.

Official
Intermediate
ubiquitoustheyubiquitousthey

issue-pick

Find, claim, and complete GitHub issues labeled for automated workflows.

Community
Intermediate