speckit-auto

Orchestrate Codex Spec Kit workflows for labeled GitHub issues.

Updated May 18, 2026
One-click install
npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-auto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-auto
Source: https://github.com/KamiJeong/tech-bridge-book/tree/main/.agents/skills/speckit-auto
Command: npx skills add https://github.com/KamiJeong/tech-bridge-book --skill speckit-auto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the Spec Kit workflow for Codex-driven repository work, helping you move from issue intake to specification, implementation, review, and delivery with consistent safety gates and token observability.

Core Features & Use Cases

  • Workflow orchestration: Coordinates the full Spec Kit sequence across intake, slicing, scheduling, spec, plan, tasks, analysis, implementation, review, integration, token reporting, commit, and PR creation.
  • Safety gating: Enforces mode-based controls such as gated, auto-implement, auto-commit, and auto-pr, while respecting approval and repository-state constraints.
  • Issue-driven automation: Interprets GitHub issue labels and trigger text to decide when to start work, how to label progress, and when to stop for clarification.
  • Use case: A project maintainer opens a labeled issue requesting a Codex-based feature change, and this Skill guides the work through the correct phases while keeping the workflow auditable.

Quick Start

Ask Codex to run the Spec Kit workflow for the active GitHub issue and follow the repository's required mode and safety gates.

Frequently Asked Questions about speckit-auto

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

FAQPage Schema
How do I automate GitHub issue processing from intake to pull request?

Spec Kit workflow orchestration automates GitHub issue processing by coordinating intake, specification, implementation, review, and draft PR creation with mandatory safety gates and token observability.

How does label-based state tracking work for Codex feature workflows?

Label-based state tracking interprets GitHub issue labels and trigger text to decide when to start work, label progress, or stop for clarification during Codex Spec Kit workflows.

What are the safety gating modes for automated repository commits?

Safety gating modes include gated, auto-implement, auto-commit, and auto-pr, enforcing approval and repository-state constraints to ensure auditable automated repository commits.

How do I track token usage during automated pull request generation?

Mandatory token observability tracks token usage during automated pull request generation by enforcing token reporting across project-scoped agents throughout the Spec Kit workflow.

Can I slice GitHub issues into smaller tasks for Codex implementation?

Yes, the Spec Kit workflow slices GitHub issues into smaller tasks, scheduling per-slice specification, implementation, and analysis before integration and draft PR creation.

When should I stop a Spec Kit workflow for human clarification?

The Spec Kit workflow stops for human clarification when GitHub issue labels or trigger text lack sufficient context to safely proceed with gated Codex implementation.