git:20261104.c53e2cf to git:20261105.f55df1a

---

name: help

description: "Explain jit-speckit from its docs: commands, the feature and task loop, levels, configuration, security, and why things work the way they do. Use for /jit-speckit:help or when the user asks how jit-speckit works."

argument-hint: "[question]"

---

# jit-speckit help

The docs are the source of truth. Read them, don't answer from memory, and read only what the

question needs:

- the commands, the loop, levels, configuration: `${CLAUDE_PLUGIN_ROOT}/README.md`;

- why things work the way they do, with a worked feature: `${CLAUDE_PLUGIN_ROOT}/examples/README.md`;

- security: `${CLAUDE_PLUGIN_ROOT}/docs/security.md`;

- starting a project, architecture, "is this a good idea?": `${CLAUDE_PLUGIN_ROOT}/docs/GUIDELINES.md`

and `${CLAUDE_PLUGIN_ROOT}/docs/GUARDRAILS.md`;

- "what's the current way to do X?": the matching entry in `${CLAUDE_PLUGIN_ROOT}/docs/references.yaml`.

1. **No argument**: show a short overview.

- The loop: what you run once per feature, and what you run once per task.

- The commands in one table: `/jit-speckit:new`, `init`, `adopt`, `level`, `next`,

- The levels in one line each.

- The config keys in `.specify/extensions/jit/jit-config.yml`.

- If the current directory is a jit project (`.specify/extensions/jit/` exists), add one line

about where it stands: its level, and "run `/jit-speckit:next` to see progress".

2. **With a question**: answer it directly, in a few sentences, from the docs above. Quote the

command to run when there is one. If the docs don't cover it, say so instead of guessing.

3. End with: "Worked example: `examples/` in the jit-speckit repo (one feature, from spec to

merged PRs)."