speckit-specify

Wrap and delegate Speckit specification commands to a source skill.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Speckit-specify provides a safe, reusable wrapper to invoke the Speckit specification workflow, reducing boilerplate and ensuring consistent spec generation.

Core Features & Use Cases

  • Wrapper orchestration: delegates a command to the source Speckit skill after parsing the input label.
  • Input routing: extracts the original command input from the user message following /speckit.specify.
  • Deterministic execution: runs the source skill with prerequisite checks, captures outputs, and returns a summary.

Quick Start

Provide a Speckit command after /speckit.specify and the wrapper executes the source skill to produce the specification.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I automate specification generation workflows with AI commands?

Automating specification generation involves wrapping and delegating Speckit tasks to a source skill. You provide a command, and the wrapper parses the input, executes prerequisite checks, and returns a validated specification summary.

What is a wrapper for AI-driven spec creation and how does it work?

A wrapper for AI-driven spec creation acts as an orchestration layer that reads the source skill, parses the user command input, and executes the task deterministically. It ensures safe execution by applying prerequisite checks before generating output.

How do I execute a Speckit specification command through an AI prompt?

To execute a Speckit specification command, you append your command input after the designated trigger. The wrapper extracts the input label, delegates the task to the source skill, and captures the executed specification output.

Does the Speckit specify wrapper require any external dependencies to run?

The Speckit specify wrapper operates without external dependencies, relying entirely on its internal orchestration logic. It reads the source skill directly before execution to ensure safe and predictable specification generation.

Why use a wrapper for AI specification orchestration instead of direct execution?

Using a wrapper for AI specification orchestration reduces boilerplate and ensures consistent spec generation across different tasks. It enforces prerequisite checks and captures outputs safely, providing a predictable summary that direct execution lacks.

What are the limitations of using a wrapper for specification task orchestration?

The wrapper is limited to processing commands that strictly follow the expected input routing format after the trigger. It requires a valid source skill to read before execution and cannot generate specifications independently without that underlying skill.