Skip to main content
command CX Codex

speckit.companion.living-show — Claude Code command: install

speckit.companion.living-show is a Claude Code command that prints requirement headings, one complete requirement, or rules tied to a file. Run it to inspect a specific part of a living spec without opening the whole document.

MIT ★ 110 updated 2026-10-19

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/speckit.companion.living-show.md
Open on GitHub

What speckit.companion.living-show does

The command runs a script that reads a living spec and prints the requested slice. --headings lists a capability’s requirement headings, --requirement returns one rule with its scenarios, and --file finds rules that describe a source file. The output is relayed without a summary or truncation. The command does not edit specs.

Living specs must be enabled, and Python 3 is required. With no configuration, the command exits without output. Run the script from the repository root at .specify/extensions/companion/scripts/resolve-spec-paths.py; add --json to get an object instead of a list.

What it helps with

  • list the requirements for one capability
  • read a requirement with its scenarios
  • find rules that describe a source file

Example prompts for the agent

  • Show the requirement headings for the billing capability.
  • Print the requirement “Refunds are recorded” with its scenarios.
  • Find the rules that describe src/billing.ts.

How to install speckit.companion.living-show

Manually: put the files in place

.claude/commands/speckit.companion.living-show.md

Call it with /speckit.companion.living-show. For all projects use ~/.claude/commands/

Questions about speckit.companion.living-show

How do I install speckit.companion.living-show in Claude Code?

Copy the command file to .claude/commands/speckit.companion.living-show.md.

What does speckit.companion.living-show do?

It prints selected parts of a living spec: requirement headings, one full requirement with scenarios, or rules associated with a file. It does not edit specs.

What does speckit.companion.living-show need to run?

Python 3 and enabled living specs. Run its script from the repository root.

Source text

speckit.companion.living-show.md · MIT
---
description: "Print one slice of a living spec — a capability's requirement headings, one requirement in full, or the requirements that describe one file (opt-in, read-only, never halts)"
---

# Show

Print part of a living spec instead of opening it. A capability's spec runs to hundreds of lines, and almost every question about one is about a single requirement: what does it say, what are its scenarios, which rules describe this file I am editing. This is the terminal twin of the load steps' selective read — same parser, same counts, no viewer required.

**Read-only** — it never edits anything, and it **never fails** (always exits success). Every unanswerable question is an answer: an unregistered capability, a missing spec file, a name that matches nothing, a file nothing claims.

This is **opt-in**. With living specs disabled (or no config), it reports nothing and exits clean.

## Prerequisites

- Verify Python is available by running `python3 --version`.
- If `python3` is not available, warn the user and skip:
  `[companion] Warning: python3 not detected; skipped the living spec slice`.

## Execution

Run one of these from the repository root, whichever the request asks for:

```bash
# every requirement heading in one capability
python3 .specify/extensions/companion/scripts/resolve-spec-paths.py --headings <capability>

# one requirement in full, including its scenarios
python3 .specify/extensions/companion/scripts/resolve-spec-paths.py --requirement "<heading>"

# the requirements that describe one source file
python3 .specify/extensions/companion/scripts/resolve-spec-paths.py --file <path>
```

Add `--capability <name>` to `--requirement` to search one capability instead of all of them. Add `--json` when a caller needs the object rather than the list.

## What each mode answers

| Mode | Answers |
|---|---|
| `--headings` | What rules does this capability state? One heading per line, in file order, with the count. |
| `--requirement` | What does this one rule say, and how would anyone know it held? The heading, the normative prose, and the scenarios. |
| `--file` | Which durable rules describe this file? Grouped by capability, most-specific capability first. |

A requirement carrying no file marker is returned by `--file` for every file its capability claims — a marker can only narrow, never starve.

## Report

Relay the script's own output. Do not summarize a requirement, paraphrase a scenario, or truncate a body: the point of the command is that a reader sees the spec's own words. Where the script reports that a capability is unregistered, has no spec file on disk, or that a name matched nothing, say that in the same terms and print the alternatives it listed.

Do **not** edit any spec as part of this command.

© alfredoperez · MIT · alfredoperez/speckit-companion

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set83

The whole set →
speckit.companion.after-tasks speckit.companion.after-tasks records task completion in .spec-context.json for Companion GUI. Intended to run from the repository root right after completing tasks. CX Codex +1 ★ 110repo stars speckit.companion.before-step The speckit.companion.before-step command records a spec-kit step’s start in .spec-context.json for the Companion GUI. Run it before specify, plan, tasks, or implement. CX Codex +1 ★ 110repo stars speckit.companion.living-coverage speckit.companion.living-coverage — a command that reports which living-spec requirements have mapped tests and which remain uncovered. It runs read-only and never halts your workflow. CX Codex +1 ★ 110repo stars bench-sync bench-sync — a command for Claude Code and Codex that bakes benchmark cells and measures the current spec-kit and Companion extension versions. Use it to track how performance changes as tools are updated. CX Codex +1 ★ 110repo stars speckit.companion.status speckit.companion.status — a command for Claude Code and Codex reads .spec-context.json and reports the active spec’s step, status, decisions, and next action. It is read-only. CX Codex +1 ★ 110repo stars speckit.plan speckit.plan runs an implementation planning workflow from a feature spec, generating research.md, data models, and API contracts. CX Codex GP ChatGPT ★ 110repo stars sandbox This command builds throwaway SpecKit sandboxes from recipes or lists available recipes and existing folders. It works with Claude Code and Codex. CX Codex +1 ★ 110repo stars release-qa release-qa is a Claude Code command that checks code before release. It compares the last version tag, runs automated and manual checks, and blocks /publish until all checks pass. CX Codex +1 ★ 110repo stars

Project sponsors

Companies that keep this analytics open