What is spec-steering-setup?

A command for creating or updating steering documents: project files that record the product purpose, technology choices, structure, and coding conventions.

It reviews the codebase, checks existing steering files, and presents inferred product, technology, and structure details for confirmation.

It gives future specification work a shared project context, so the agent does not need to rediscover these details each time.

spec-steering-setup — Command by Pimzino

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/pimzino/claude-code-spec-workflow/spec-steering-setup

Clone the repo

git clone --depth 1 https://github.com/Pimzino/claude-code-spec-workflow

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 845 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00845
Opus 5	$0.00000	$0.00423
Sonnet 5	$0.00000	$0.00169
Haiku 4.5	$0.00000	$0.00085

Measured yesterday against content hash 3373791eb8f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-steering-setup scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

spec-steering-setup — 100% identical, 0 lines differ

src/markdown/commands/spec-steering-setup.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec Steering Setup Command

Create or update steering documents that provide persistent project context.

Usage

/spec-steering-setup

Instructions

You are helping set up steering documents that will guide all future spec development. These documents provide persistent context about the product vision, technology stack, and project structure.

Process

Check for Existing Steering Documents
- Look for .claude/steering/ directory
- Check for existing product.md, tech.md, structure.md files
- If they exist, load and display current content
Analyze the Project
- Review the codebase to understand:
  - Project type and purpose
  - Technology stack in use
  - Directory structure and patterns
  - Coding conventions
  - Existing features and functionality
- Look for:
  - package.json, requirements.txt, go.mod, etc.
  - README files
  - Configuration files
  - Source code structure
Present Inferred Details
- Show the user what you've learned about:
  - Product: Purpose, features, target users
  - Technology: Frameworks, libraries, tools
  - Structure: File organization, naming conventions
- Format as:
```
Based on my analysis, here's what I've inferred:

**Product Details:**
- [Inferred detail 1]
- [Inferred detail 2]

**Technology Stack:**
- [Inferred tech 1]
- [Inferred tech 2]

**Project Structure:**
- [Inferred pattern 1]
- [Inferred pattern 2]
```
- Ask: "Do these inferred details look correct? Please let me know which ones to keep or discard."
Gather Missing Information
- Based on user feedback, identify gaps
- Ask targeted questions to fill in missing details:
  
  Product Questions:
  - What is the main problem this product solves?
  - Who are the primary users?
  - What are the key business objectives?
  - What metrics define success?
  Technology Questions:
  - Are there any technical constraints or requirements?
  - What third-party services are integrated?
  - What are the performance requirements?

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 112 lines · 0 tokens per session scan A 3373791eb8f0

Subscribe to this mod's changes

spec-steering-setup is a command published in the GitHub repository Pimzino/claude-code-spec-workflow (3,853 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 845 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

spec-steering-setup

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Spec Steering Setup Command

Usage

Instructions

Process

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement