core

Facilitate an 11-step spec-driven development workflow with hard gates and peer review.

9|Updated May 27, 2026
One-click install
npx skills add https://github.com/kamioj/spec-workflow --skill core-kamioj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core
Source: https://github.com/kamioj/spec-workflow/tree/main/core
Command: npx skills add https://github.com/kamioj/spec-workflow --skill core-kamioj

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of managing large changes in a disciplined and reversible manner by guiding the user through a 11-step spec-driven development workflow.

Core Features & Use Cases

  • 11 Independent Commands: Each stage of the workflow can be executed independently, allowing for re-entrant, interruptible, and re-runnable processes.
  • Explicit Hard Gating: Ensures that the workflow stops at critical points, such as the design and implementation phases, to enforce quality control.
  • Heterogeneous Peer Review: Allows for multiple reviewers, including Codex, to provide feedback on the changes, ensuring a robust review process.
  • Anti-Cheating Measures: Prevents malicious or incorrect actions by enforcing strict rules and verification processes.
  • Use Case: Ideal for developers working on complex projects where changes require careful planning and execution.

Quick Start

To initiate the spec-driven development workflow, type /spec:workflow <task> followed by the specific task you wish to work on.

Frequently Asked Questions about core

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

FAQPage Schema
How do I manage large software changes with spec-driven development?

Spec-driven development manages large software changes by guiding you through an 11-step workflow with explicit hard gates, ensuring disciplined, controlled, and reversible updates.

What are hard gates in a software development workflow?

Hard gates in a software development workflow enforce quality control by stopping the process at critical design and implementation phases, preventing progression until review criteria are met.

How do I enforce peer review and anti-cheating measures during code changes?

You can enforce peer review and anti-cheating measures by adopting a workflow that supports heterogeneous reviewers and strict verification rules, preventing malicious or incorrect actions during implementation.

Can I pause and resume a multi-step change management workflow?

Yes, this change management workflow uses independent commands for each stage, making the process re-entrant, interruptible, and re-runnable so you can pause and resume large software changes easily.

Is a spec-driven workflow suitable for small software updates?

Spec-driven workflows involve thorough planning and multiple review stages, making them ideal for complex projects requiring careful execution rather than small, rapid software updates.

How do I start a spec-driven development workflow?

You start a spec-driven development workflow by initiating the process with a specific task command, which then guides you sequentially through planning, design, and implementation phases.