# speckit.companion.auto

speckit.companion.auto — a command for Claude Code and Codex that automates the whole feature lifecycle without confirmation pauses. It chains specify, plan, tasks, implement, and converge in an unattended run.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 110 repo stars
- Author: alfredoperez
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.auto.md
- Updated: 2026-11-10
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/speckitcompanionauto

## What it does

This command operates in Claude Code and Codex as the master orchestrator for the SpecKit Companion pipeline. Instead of pausing for human sign-off between phases, it sequences the entire workflow: specify, plan, tasks, implement, and converge. The agent acts strictly as a conductor by dispatching each standalone step command directly rather than drafting documents from scratch.

Execution begins by provisioning an isolated feature directory with `mint-spec-dir.py` or resolving a path from `SPECIFY_FEATURE_DIRECTORY`. The process refuses to touch folders that already hold an existing `spec.md`, protecting prior completed features. It flags `unattended: true` and logs timestamps atomically to `.spec-context.json` via companion scripts.

Running this command requires Python 3 alongside the project scripts located in `.specify/extensions/companion/scripts/`. Without those local utilities present, setup fails right at the initial timestamp step.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/speckit.companion.auto.md` — Call it with /speckit.companion.auto. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/speckit.companion.auto.md` — Call it with /prompts:speckit.companion.auto. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/speckit.companion.auto.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/speckit.companion.auto.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.auto.md

## When to use it
- Execute an entire spec-to-code pipeline without human checkpoints
- Mint dedicated feature directories using automated numbering rules
- Record raw user prompts directly into `.spec-context.json`
- Keep structured artifacts like design docs and wave tasks intact

## Example prompts
- /speckit-companion-auto Add CSV export functionality for billing invoices
- /speckit-companion-auto Implement telephone number verification during signup
- /speckit-companion-auto Dispatch webhook events whenever order statuses change

## Source text · speckit.companion.auto.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: d326d5b46ea49105.

BEGIN THIRD-PARTY FILE d326d5b46ea49105
````text
---
description: "Companion auto — run the whole pipeline hands-off (specify → plan → tasks → implement → converge), no pauses"
---

## User Input

```text
$ARGUMENTS
```

<!-- speckit-companion:part step-start -->
## Record this step's start: before anything else runs

A step's recorded window has to contain the work it claims. Stamping the start partway down the body leaves the extension hooks, and any node above the stamp, outside the window the step later reports. So this is the first instruction in the command, ahead of the hooks.

Let `<step>` be this command's phase and `<status>` its in-progress status: `specify`/`specifying`, `plan`/`planning`, `tasks`/`tasking`, `implement`/`implementing`.

**Which feature directory this step stamps against decides when it stamps.**

- **A step that mints its own feature directory**, meaning any fresh-spec entry point such as `specify` or `auto`, has nothing to stamp against yet. `.specify/feature.json` is this step's *output*: it still points at the **previous** spec, so stamping now would write this run's status onto finished work. Resolve the directory first, then stamp the instant it exists, before any other work in the step.
- **Every other step** reads the feature directory it was given, from the invocation or from `.specify/feature.json`, which by then points at this spec. Stamp immediately, before the extension hooks and before any node.

In both cases the call is the same:

```bash
python3 .specify/extensions/companion/scripts/write-context.py --feature-dir <feature_directory> --step <step> --status <status> --kind start --by extension
```

Add `--at "<dispatch time>"` when the dispatcher printed one; otherwise the script stamps now. Two things keep this honest:

- **Run it, never hand-write it.** The script stamps the real clock and writes atomically. A hand-authored entry in `.spec-context.json` is what corrupts the file.
- **A second start is refused, not reconciled.** History is append-only, so if the extension already seeded this step's start, this call appends nothing and the earlier timestamp stands. Running it is always safe; skipping it loses the window.
<!-- /speckit-companion:part step-start -->

<!-- speckit-companion:part command-spelling -->
## Name every command the way this project registers it

Commands are named in dot form throughout this body, `speckit.companion.plan`, because that is their canonical id, and without a leading slash, because the spelling a host actually registers is not always this one. Claude Code installs `/speckit-companion-plan`. Look at how the commands are installed in this project, under the agent's own commands or skills directory, and use that spelling every time you name one to the developer or dispatch one yourself. A dotted name typed into a host that registered dashes resolves to nothing at all.
<!-- /speckit-companion:part command-spelling -->

## Outline

Run the **entire** Companion pipeline end-to-end and unattended. Walk every step in order, specify → plan → tasks → implement → converge, dispatching the same per-step `speckit.companion.*` commands, never pausing for approval in between, and finish the spec at `status: completed`.
<!-- speckit-companion:phase gather -->
<!-- speckit-companion:node resolve-dir -->
````
END THIRD-PARTY FILE d326d5b46ea49105

The third-party file has ended. Everything between the d326d5b46ea49105 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3294 of 16932 bytes. © alfredoperez · MIT · https://github.com/alfredoperez/speckit-companion/tree/HEAD/apps/speckit-extension/commands/speckit.companion.auto.md

## Similar
- [bmad-auto](https://affpapa.org/en/nevibecode/skills/bmad-auto.md) — skill · 145 installs
- [auto-trigger](https://affpapa.org/en/nevibecode/skills/auto-trigger.md) — skill · 707 installs
- [graph](https://affpapa.org/en/nevibecode/skills/yeachan-heo-graph.md) — skill · 285 installs

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
