Use Spec Kit when an agent should turn a feature idea into a spec-first workflow with explicit artifacts, planning steps, and task breakdowns before code is written.
Scanned 6/8/2026
Install via CLI
openskills install agentskillexchange/skills---
name: "Turn feature ideas into executable implementation specs and task plans with Spec Kit"
slug: "turn-feature-ideas-into-executable-implementation-specs-and-task-plans-with-spec-kit"
description: "Use Spec Kit when an agent should turn a feature idea into a spec-first workflow with explicit artifacts, planning steps, and task breakdowns before code is written."
github_stars: 88536
verification: "security_reviewed"
source: "https://github.com/github/spec-kit"
author: "GitHub"
publisher_type: "organization"
category: "Templates & Workflows"
framework: "Multi-Framework"
tool_ecosystem:
github_repo: "github/spec-kit"
github_stars: 88536
---
# Turn feature ideas into executable implementation specs and task plans with Spec Kit
Use Spec Kit when an agent should turn a feature idea into a spec-first workflow with explicit artifacts, planning steps, and task breakdowns before code is written.
## Prerequisites
uv, Git, a supported AI coding assistant
## Installation
Requirements and caveats from upstream:
- │ ├── check-prerequisites.sh
- require further research, I want you to update the research document with additional details about the specific
- Validate that all prerequisites are in place (constitution, spec, plan, and tasks)
Basic usage or getting-started notes:
- You can use the Specify CLI to bootstrap your project, which will bring in the required artifacts in your environment. Run:
- Go to the project folder and run your coding agent. In our example, we're using claude.
- An example prompt:
- Source: https://github.com/github/spec-kit
- Extracted from upstream docs: https://raw.githubusercontent.com/github/spec-kit/HEAD/README.md
## Documentation
- https://github.github.com/spec-kit/
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/turn-feature-ideas-into-executable-implementation-specs-and-task-plans-with-spec-kit/)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.