speckit-git-feature

Delegate Speckit git feature workflow execution to a source skill.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill speckit-git-feature-opensoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-git-feature
Source: https://github.com/opensoft/dartwing-ocr-pipeline/tree/main/plugins/speckit/skills/speckit-git-feature
Command: npx skills add https://github.com/opensoft/dartwing-ocr-pipeline --skill speckit-git-feature-opensoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delegates execution of the Speckit git feature workflow to a source skill, providing a consistent, single-entry interface.

Core Features & Use Cases

  • Delegates the Speckit git feature workflow to the underlying source skill.
  • Routes the input that follows the command label to the source skill and preserves branch creation behavior.
  • Use Case: Teams can trigger a Speckit feature branch via a stable wrapper without embedding the implementation details.

Quick Start

Trigger the wrapper with your command targeting a Speckit feature branch; input after the label is passed to the source skill for execution.

Frequently Asked Questions about speckit-git-feature

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

FAQPage Schema
How do I automate git feature branch creation with a consistent workflow?

Automating git feature branch creation is handled by delegating execution to a source skill, providing a single-entry interface that routes input after the command label to preserve branch creation behavior.

What is a wrapper skill for git feature workflows?

A wrapper skill for git feature workflows delegates execution to an underlying source skill, offering a stable entry point that triggers a Speckit feature branch without embedding implementation details.

How do I trigger a Speckit git feature branch using a wrapper interface?

To trigger a Speckit git feature branch, use the wrapper with your command; the input following the label is passed directly to the source skill for execution.

Do I need to configure the source skill separately before using this workflow wrapper?

Using this workflow wrapper requires the underlying source skill to be present, as the wrapper reads and routes input to the source skill to execute the defined branch creation workflow exactly.

Why use a wrapper to delegate git feature branch workflows instead of direct execution?

Using a wrapper to delegate git feature branch workflows provides a consistent, single-entry interface, allowing teams to trigger branches without embedding the source skill's implementation details.

What happens to input data after the command label in a Speckit workflow?

Input data after the command label is routed directly to the source skill, ensuring the Speckit feature branch workflow executes exactly as defined by the underlying implementation.