speckit

Name: speckit
Availability: InStock
Author: yoyooyooo

Route Spec-Driven Development stages and write decisions into spec-kit artifacts.

4|1|Updated Dec 11, 2025

Search Tags:#workflow orchestration #spec-driven development #spec writeback #planning and tasks #acceptance review #multi-spec groups

Ready to run

npx skills add https://github.com/yoyooyooo/logix --skill speckit-yoyooyooo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: speckit
Source: https://github.com/yoyooyooo/logix/tree/main/.codex/skills/speckit
Command: npx skills add https://github.com/yoyooyooo/logix --skill speckit-yoyooyooo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps teams avoid spec drift by routing each conversation decision into the correct Spec Kit artifact at the right stage, so spec → plan → tasks → implementation → acceptance stays consistent.

Core Features & Use Cases

Unified stage router: Run a single command in the right stage to drive the Spec-Driven Development workflow end-to-end.
Decision writeback to spec-kit outputs: Automatically updates the corresponding products (spec.md, plan.md, tasks.md, checklists/*, and constitution memory) when the user makes key decisions that affect outcomes.
Safety-gated behavior: Stays silent during casual chat/brainstorming, and triggers only when explicit changes/decisions require product updates.
Deep validation stages: Supports analyze and acceptance to cross-check coded points and drift after implementation.
Multi-spec orchestration: Handles Spec Groups via group dispatch and multi-spec acceptance.

Quick Start

Use the speckit skill to run a stage router for your Spec Kit repo by invoking: $speckit plan 025-my-feature.

Frequently Asked Questions about speckit

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

FAQPage Schema

How do I prevent spec drift during spec-driven development?▼

Spec drift is prevented by routing stage-ordered decisions directly into spec-kit artifacts. This approach automatically updates outputs like spec.md, plan.md, and tasks.md only when explicit decisions are made, keeping the entire workflow consistent.

What is the best way to orchestrate multi-spec workflow groups?▼

Orchestrating multi-spec workflow groups is best handled by a unified stage router with group dispatch capabilities. This drives the workflow end-to-end and manages multi-spec acceptance to keep all related specifications aligned.

How do I automatically write decisions back to spec artifacts?▼

Decisions are written back to spec artifacts by using a stage router that enforces update-only-on-decision behavior. When a key decision is reached, it automatically updates corresponding outputs like spec.md, plan.md, tasks.md, and checklists.

Can I run spec planning and acceptance review in Python3?▼

Yes, you can run spec planning and acceptance review in Python3. The workflow uses script resources within the Python3 environment to route stages, enforce read-before-write constraints, and cross-check coded points for drift after implementation.

Does spec-driven development work during casual brainstorming sessions?▼

Spec-driven development tools with safety-gated behavior stay silent during casual brainstorming sessions. The workflow triggers only when explicit changes or decisions require product updates, preventing premature modifications to spec artifacts.