speckit-rules

Coordinates Spec Kit multi-agent workflow rules for repository tasks and safety gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps coordinate Spec Kit and Codex workflows for multi-step repository changes while keeping the process safe, gated, and predictable.

Core Features & Use Cases

  • Workflow sequencing: Follows the required order for intake, slicing, scheduling, spec creation, analysis, implementation, review, and integration.
  • Execution mode control: Distinguishes between plan-only, gated, auto-implement, auto-commit, and auto-pr modes to prevent unsafe actions.
  • Safety and repository rules: Enforces stop conditions, path conventions, and commentary requirements for changes, commits, and PR actions.

Quick Start

Ask the assistant to apply the Spec Kit rules to your current repository task and guide the work through the correct gated workflow.

Frequently Asked Questions about speckit-rules

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

FAQPage Schema
How do I coordinate multi-agent workflows for repository tasks safely?

Coordinating multi-agent workflows safely requires applying Spec Kit rules to sequence tasks through gated phases, enforcing stop conditions and explicit approvals before destructive actions.

What is the correct workflow sequence for Spec Kit planning and implementation?

The Spec Kit workflow sequence follows a strict order: intake, slicing, scheduling, spec creation, analysis, implementation, review, and integration for repository tasks.

How do I prevent unsafe auto-commit or auto-pr actions in Codex?

Preventing unsafe actions in Codex involves using execution mode controls like plan-only or gated modes, which require explicit approval before auto-commit, auto-pr, or publishing operations.

Can I control execution modes for automated Spec Kit repository changes?

Yes, you can control execution modes for Spec Kit changes by distinguishing between plan-only, gated, auto-implement, auto-commit, and auto-pr modes to match your desired safety level.

What stop conditions apply when running Spec Kit multi-agent operations?

Stop conditions for Spec Kit operations enforce compliance with Codex path conventions, token observability, and commentary requirements, halting execution before destructive or publishing actions without approval.