skills.rest
kargarisaac
kargarisaacCOMMUNITY
Explore all skills by this author →
𝕏@kargarisaacGitHub

speckit

Generate spec, decisions, plan, and tasks artifacts for spec-first features.

8|Updated Jan 14, 2026
Search Tags:#documentation#spec#tasks#plan#feature#specs
One-click install
npx skills add https://github.com/kargarisaac/speckit-skill --skill speckit-kargarisaac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit
Source: https://github.com/kargarisaac/speckit-skill/tree/main/speckit
Command: npx skills add https://github.com/kargarisaac/speckit-skill --skill speckit-kargarisaac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Spec-driven development workflow scaffolding and guidance for generating and maintaining repos that organize features under specs/###-feature directories.

Core Features & Use Cases

  • Spec-first workflow: spec → decisions → plan → tasks → implement
  • ADRs: decisions.md to capture the "why"
  • Four core artifacts per feature: spec.md, decisions.md, plan.md, tasks.md
  • Templates & conventions: assets/templates provide a consistent starting point for artifacts

Quick Start

Use speckit new <feature description> to generate the spec, decisions, plan, and tasks for your feature.

Frequently Asked Questions about speckit

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

FAQPage Schema
How do I automate spec-driven development documentation for new features?▼

Spec-driven development documentation is automated by scaffolding four core artifacts: spec.md, decisions.md, plan.md, and tasks.md. You can generate these templated files instantly using the 'new' command with a feature description.

What is included in a spec-first feature workflow?▼

A spec-first feature workflow includes four core artifacts: spec.md, decisions.md, plan.md, and tasks.md. It progresses from defining the spec to capturing architectural decisions, planning, and generating tasks before implementation.

How do I organize feature specs and tasks in a repository?▼

Organize feature specs and tasks by placing the generated artifacts within dedicated 'specs/###-feature' directories. This structure enforces frontmatter requirements and maintains consistent documentation contracts across the repository.

Can I use templates to standardize feature planning and decisions documentation?▼

Yes, you can standardize feature planning and decisions documentation using provided asset templates. These templates serve as a consistent starting point for generating spec.md, decisions.md, plan.md, and tasks.md files.

Does spec-driven development require specific directory structures for feature artifacts?▼

Spec-driven development requires organizing artifacts under 'specs/###-feature/' directories. This specific directory structure is necessary to enforce frontmatter requirements and maintain the four-core-artifact contracts.

Related Skills

Explore More Software Engineering Skills→
Ab0umarAb0umar

speckit-git-validate

Validate Git branch names against feature-branch naming rules.

Community
Intermediate
ThalfmanThalfman

to-issues

Convert project plans into issues with labels and dependencies in an issue tracker.

Community
Intermediate
rkz91rkz91
264

create-skill

Create and validate Cursor Skills with SKILL.md frontmatter and documentation templates.

Community
Intermediate
yoshisadayoshisada

kiln-init

Initialize kiln in an existing repository with harness, scaffolding, and workflow hooks.

Community
Intermediate