All directories
SkillEngineeringProduct

Spec Kit

github/spec-kit

GitHub’s spec-kit for spec-driven development with agents — specify, plan, then implement. GitHub: github/spec-kit (~126k stars).

Open on GitHubBrowse more skills
00

GitHub repository

https://github.com/github/spec-kit
01

Overview

Spec Kit is the open-source project at github/spec-kit on GitHub (https://github.com/github/spec-kit). GitHub’s spec-kit for spec-driven development with agents — specify, plan, then implement. Category on LimeDock: ai-powered. Approximate community size: ~126k GitHub stars. Repo (copy/paste): https://github.com/github/spec-kit This LimeDock Directories page explains what it is and how teams use it in plain English — so searches for the GitHub project can land on a practical guide.

SaaSOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

Book a workflow call
02

Link

https://github.com/github/spec-kit
03

Installation guide

Open the GitHub repository, then follow the README for your stack.

Official GitHub repository: https://github.com/github/spec-kit GitHub path: github/spec-kit

How to open it: 1. Copy this URL: https://github.com/github/spec-kit 2. Clone or follow the README install for your OS / stack. 3. Start with the smallest example in their docs before production use.

04

How to use it

**Simple example** PRs are messy because agents code before the spec is clear.

1. Clone github/spec-kit. 2. Follow the specify → plan → implement flow on a small ticket. 3. Keep the spec in-repo as the source of truth.

05

Example prompts

  • “Use Spec Kit to write a spec for this feature request.”
  • “Turn this vague ticket into a Spec Kit plan.”
  • “How do we enforce spec-first in Claude Code?”
06

Use cases and examples

  • Evaluate github/spec-kit for your stack
  • Onboard a teammate to Spec Kit with a shared checklist
  • Compare Spec Kit against tools you already pay for
  • Capture lessons in your internal wiki after a pilot
07

Prerequisites

  • GitHub-centric workflow
  • Team buy-in for specs before code
08

Tips

  • Specs prevent agent thrash.
  • Start with bugs/features that have clear acceptance tests.