Does Spec Kit replace a custom skills pack?

No. Spec Kit installs its /speckit-* skills; your ops pack should coexist with clear names so you don’t overwrite upstream ids.

Where do skills install for Cursor?

Spec Kit’s Cursor path lands under .cursor/skills. Prefer project-scoped packs so the repo carries them.

Can skills replace AGENTS.md?

No. AGENTS.md remains the portable router; skills are on-demand procedures under that router.

How do I avoid forking Spec Kit?

Call Spec Kit skills as-is; put company-specific workflows in your own skill ids. Document both in AGENTS.md.

/free, then /products/agent-starter-kit ($47) for an opinionated ops pack under the Spec Kit path.

Spec Kit → `.cursor/skills` install guide

Spec Kit’s Cursor path is one command: specify init --integration cursor-agent. That install lands Spec Kit skills under .cursor/skills (invoked as /speckit-* style commands in the agent). Your custom ops pack should coexist—namespace team skills so you never overwrite upstream ids. Don’t fork Spec Kit; operationalize it under an AGENTS.md router. For product UI and migrate flags, follow Cursor’s skills and rules docs—this post is an ops install guide, not a help-center clone. Soft path: /free; pack: Agent Starter Kit ($47).

Who this is for

You want Spec Kit’s `/speckit-*` flows in Cursor and a team skills pack—without colliding ids, forking upstream, or pasting install docs into always-on rules. Companion decision tree: Cursor rules vs skills — when to use each (and how Spec Kit fits).

Official Spec Kit and Cursor docs remain the authority for flags and UI. This post owns the desk layout: where skills land, how a custom pack sits beside them, and what stays in `AGENTS.md`.

Install path (point to upstream)

From a project that already uses Spec Kit’s CLI:

bash

specify init --integration cursor-agent

Expect Spec Kit skills under `.cursor/skills`. Prefer project-scoped installs so the repo carries the pack for shared desks. User-level skills are fine for personal shortcuts—document which is which in `AGENTS.md`.

If rules already bloated before you add Spec Kit, use Cursor’s official `/migrate-to-skills` on-ramp. Point teammates at Cursor docs; don’t restate the whole help center here.

Pack layout: coexist, don’t collide

Layer	Owns	Do not
Spec Kit skills (`/speckit-*`)	Upstream spec-driven flows after `specify init --integration cursor-agent`	Fork / rebrand / overwrite their skill ids
Custom ops pack (your `SKILL.md` tree)	Team procedures (verify, ship checklist, desk seats)	Share filenames/ids with Spec Kit skills
Thin Cursor rules	Short globs / alwaysApply constraints	Paste Spec Kit or pack guides into always-on rules
AGENTS.md	Portable router: which skills exist, project vs user, verify / approval stops	Dump full skill prose into the contract

Coexist checklist:

Keep Spec Kit skill ids intact.
Namespace your ops pack (clear prefixes / folders).
List Spec Kit vs team skills in `AGENTS.md`.
Prefer project-scoped skills for anything the desk shares.

Skills do not replace AGENTS.md

Skills are on-demand procedures under Cursor (and Spec Kit’s Cursor path). `AGENTS.md` remains the portable operating contract across harnesses—commands, verify, guardrails. Same split as the rules vs skills post: router stays portable; skills stay reusable workflows.

What the Agent Starter Kit is for

The Agent Starter Kit ($47) packages an opinionated ops skills pack + `AGENTS.md` router that lives beside Spec Kit under `.cursor/skills`—not a Spec Kit fork. Soft path: /free first if you want the coexist/layout mindset before buying.

Soft next step

Run `specify init --integration cursor-agent`, keep Spec Kit ids intact, and namespace your ops pack under the same `.cursor/skills` tree—router in `AGENTS.md`, not a fork. When you want the pack packaged, use /free for the starter desk, or the Agent Starter Kit ($47) for the opinionated skills pack + harness templates. No rush—ship the coexist checklist into your own runbook either way.