init

Included with Lifetime

$97 forever

Use when the user invokes $spec-kit:init or /spec-kit:init, or asks to bootstrap .specify/ for streamlined spec-driven development.

General

What this skill does

# Spec Kit Init

This is a user-invoked Spec Kit workflow. Treat user text after the invocation as the workflow input.

## Plugin Root

Use the spec-kit plugin root when running bundled scripts. In Claude Code, `${CLAUDE_PLUGIN_ROOT}` resolves to this plugin root. If that variable is unavailable, resolve the plugin root as the directory two levels above this `SKILL.md`.

Initialize `.specify/` in the current project for streamlined, brownfield-aware
spec-driven development.

## Steps

1. Inspect the current directory:
- Is it a git repo?
- Is the worktree dirty?
- Which package/tooling files and repo guidance files exist?

2. Create missing directories only:
```text
.specify/
├── memory/
│ ├── constitution.md
│ └── project-context.md # local-only, gitignored
└── specs/
```

3. If `.specify/memory/constitution.md` does not exist, create this placeholder:
```markdown
# Project Constitution

> Run `/spec-kit:constitution` to generate pragmatic project guardrails.

**Version**: 0.0.0 | **Ratified**: TODO | **Last Amended**: TODO
```

4. Create or refresh local-only `.specify/memory/project-context.md` by running
the bundled detector when available. The detector should also add the path to
`.gitignore` in git repositories:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/detect-project-context.sh" --write
```
If unavailable, write a minimal context file manually from the inspection and
add `.specify/memory/project-context.md` to `.gitignore`.

5. Do not run `git init` unless the user explicitly asked for it. If this is not
a git repo, report that branch-based feature detection will require
`SPECIFY_FEATURE` or explicit feature selection.

6. Report:
- Files/directories created or already present
- Detected stack/tooling summary
- Whether git was left unchanged
- Next step: `/spec-kit:constitution <project context>`

Files: 2

Size: 2.2 KB

Complexity: 11/100

Category: General

Source: https://github.com/grailautomation/claude-plugins/tree/main/spec-kit/skills/init

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts