spec-kit-bridge

Coordinate GitHub Spec Kit workflows by mapping spec phases to domain skills.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GiantCroissant-Lunar/fantasim-world --skill spec-kit-bridge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-kit-bridge
Source: https://github.com/GiantCroissant-Lunar/fantasim-world/tree/main/.agent/skills/spec-kit-bridge
Command: npx skills add https://github.com/GiantCroissant-Lunar/fantasim-world --skill spec-kit-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as procedural glue between GitHub Spec Kit and the fantasim-world domain skills, ensuring that each feature worktree adheres to the one-feature-per-worktree invariant and that spec phases are correctly mapped to the appropriate domain skills.

Core Features & Use Cases

  • Orchestrates the Specify, Plan, Tasks, and Implement phases by routing to the correct domain skills
  • Enforces the one-feature-per-worktree invariant and validates worktree/branch state
  • Supports both CLI and slash-command interfaces for working with GitHub Spec Kit
  • Enables parallel agent execution by clearly delineating task boundaries and phase responsibilities
  • Integrates with existing domain skills to keep specs structured for collaboration across teams

Quick Start

Start a new spec worktree for a feature using the Taskfile or git worktree, then run:

  • Create a new spec worktree: task spec:new <feature-name>
  • Enter the worktree: cd ../fantasim-world--<feature-name>
  • Run the Specify phase with the preferred interface: task spec:specify FEATURE=<feature-name> or /speckit.specify
  • Continue with Plan and Tasks phases as guided by the workflow: task spec:plan FEATURE=<feature-name>, task spec:tasks FEATURE=<feature-name>
  • Implement and finalize: follow domain skills for Implement and then merge PR

Frequently Asked Questions about spec-kit-bridge

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

FAQPage Schema
How do I coordinate GitHub Spec Kit workflows across multiple git worktrees?▼

To coordinate GitHub Spec Kit workflows, you map spec phases to domain skills while enforcing a one-feature-per-worktree invariant, ensuring parallel agents stay isolated within their respective git worktrees and branch states.

How does spec phase mapping work for parallel agent execution?▼

Spec phase mapping routes the Specify, Plan, Tasks, and Implement phases to the correct domain skills, clearly delineating task boundaries and phase responsibilities so parallel agents can execute concurrently without overlapping logic.

Can I use slash commands instead of CLI to trigger spec-driven workflow orchestration?▼

Yes, you can trigger spec-driven workflow orchestration using both CLI (via Taskfile commands like task spec:specify) and slash-command interfaces (like /speckit.specify) to route phases to the appropriate domain skills.

What is the one-feature-per-worktree invariant in spec-driven development?▼

The one-feature-per-worktree invariant is a validation rule ensuring each git worktree and branch isolates a single feature, preventing scope bleed and guiding parallel agents during the spec lifecycle orchestration.

How do I start a new spec worktree for feature-driven development?▼

To start a new spec worktree, run task spec:new <feature-name> to create the branch, enter the directory with cd ../fantasim-world--<feature-name>, and then execute the Specify, Plan, and Tasks phases sequentially.

Do I need existing domain skills to use this spec-kit bridge orchestration?▼

Yes, this orchestration acts as procedural glue rather than domain logic, requiring existing domain skills to handle the actual implementation during the Implement phase after the Specify, Plan, and Tasks phases are mapped.