@allthingsclaude/blueprints 0.3.0-beta.25 → 0.3.0-beta.26

package/content/agents/plan.md

@@ -323,7 +323,7 @@ Examples (assuming 2 plans already exist — `PLAN_00_INITIAL.md` and `PLAN_01_A
 
 ## Update Active Plan Tracker (MANDATORY)
 
-**This step is NOT optional.** After writing the plan file, you MUST create or update `{{STATE_FILE}}`. Other commands (`/auto`, `/kickoff`, `/implement`, `/parallelize`) depend on this file to detect the active plan. If STATE.md is missing, the entire workflow breaks.
+**This step is NOT optional.** After writing the plan file, you MUST create or update `{{STATE_FILE}}`. Other commands (`/autopilot`, `/kickoff`, `/implement`, `/parallelize`) depend on this file to detect the active plan. If STATE.md is missing, the entire workflow breaks.
 
 ```bash
 mkdir -p $(dirname {{STATE_FILE}})

package/content/agents/showcase.md

@@ -326,7 +326,7 @@ The hero is the first impression — make it count.
 
 ## Integration with Other Commands
 
-When called from `/auto`, `/implement`, or `/parallelize`:
+When called from `/autopilot`, `/implement`, or `/parallelize`:
 - This agent handles any plan task tagged as "landing page", "homepage design", "marketing page", or similar
 - It replaces the generic implement agent for these specific tasks
 - After completion, control returns to the calling workflow

package/content/commands/{auto.md → autopilot.md}

@@ -4,7 +4,7 @@ argument-hint: [--full] [feature description or plan name]
 author: "@markoradak"
 ---
 
-# Auto Mode
+# Autopilot Mode
 
 Full autonomous development loop. I'll take it from idea to committed code on a feature branch.
 
@@ -34,9 +34,9 @@ $ARGUMENTS
 
 ---
 
-## Auto Mode Protocol
+## Autopilot Protocol
 
-You are now in **AUTO MODE** — a full development loop that orchestrates the entire workflow from idea to committed code. Follow these steps precisely and in order.
+You are now in **AUTOPILOT MODE** — a full development loop that orchestrates the entire workflow from idea to committed code. Follow these steps precisely and in order.
 
 ### Step 0: Parse Arguments
 
@@ -296,7 +296,7 @@ Review security report:
 After everything is done (or stopped), provide a final summary:
 
 ```markdown
-**Auto Mode Complete**
+**Autopilot Complete**
 
 **Branch**: `feat/{name}`
 **Plan**: {NAME}
@@ -319,14 +319,14 @@ After everything is done (or stopped), provide a final summary:
 **Next Steps**:
 - Review changes: `git log main..feat/{name} --oneline`
 - Create PR when ready: `gh pr create`
-- Or continue working: `/auto` (will resume from STATE.md)
+- Or continue working: `/autopilot` (will resume from STATE.md)
 ```
 
 ---
 
 ## Commit Checkpoint Rules
 
-Auto mode commits **early and often** using the commit agent (`subagent_type="commit"`). The commit agent determines the right prefix (`feat:`, `fix:`, `refactor:`, `chore:`, `docs:`, etc.) based on the changes.
+Autopilot commits **early and often** using the commit agent (`subagent_type="commit"`). The commit agent determines the right prefix (`feat:`, `fix:`, `refactor:`, `chore:`, `docs:`, etc.) based on the changes.
 
 **When to commit:**
 - After bootstrap scaffolding is created
@@ -395,7 +395,7 @@ Auto mode commits **early and often** using the commit agent (`subagent_type="co
 - Mark all tasks as `✅` in the plan's task tables
 - Set `**Status**` to `✅ Complete`
 
-If `/auto` is interrupted or paused, ensure STATE.md reflects where it stopped so the next `/auto` run can resume correctly. Plan document checkboxes are updated by the implement/parallelize agents.
+If `/autopilot` is interrupted or paused, ensure STATE.md reflects where it stopped so the next `/autopilot` run can resume correctly. Plan document checkboxes are updated by the implement/parallelize agents.
 
 ### Keep the User Informed
 - Brief status updates between major steps

package/content/commands/brainstorm.md

@@ -26,7 +26,7 @@ Before brainstorming, quickly assess the current project:
 **Is this an empty/new project?** If there are fewer than 5 source files and no meaningful project configuration, this is likely a **new project**. In that case:
 - Mention to the user that this looks like a new project and brainstorming is a great starting point
 - The brainstorm should focus heavily on **tech stack decisions** (see Step 1 below)
-- When brainstorming is complete, suggest `/auto` which will handle planning, bootstrapping, and implementation end-to-end
+- When brainstorming is complete, suggest `/autopilot` which will handle planning, bootstrapping, and implementation end-to-end
 
 ## Brainstorming Framework
 
@@ -112,7 +112,7 @@ Throughout brainstorming, actively use the `/critique`, `/verify`, and `/challen
 
 If the user shares images during brainstorming (screenshots, mockups, design references, wireframes, inspiration), **track their file paths**. These are critical for downstream plan creation.
 
-When brainstorming is complete and you suggest `/plan` or `/auto`:
+When brainstorming is complete and you suggest `/plan` or `/autopilot`:
 - Mention the collected image paths in your handoff so the plan agent copies them to `{{TASKS_DIR}}/references/`
 - If images were shared via the conversation (e.g., user provided a file path or pasted a screenshot), note them explicitly in the brainstorm summary
 
@@ -140,14 +140,14 @@ Once we've thoroughly explored the problem space, settled on a tech stack, and c
 | Command | What it does |
 |---|---|
 | `/bootstrap {NAME}` | Generate a plan + bootstrap script to scaffold the project. Good when you want to review the scaffolding before building. |
-| `/auto {NAME}` | Full autonomous loop — planning, bootstrapping, implementation, and commit. Good when you want to go hands-off. |
+| `/autopilot {NAME}` | Full autonomous loop — planning, bootstrapping, implementation, and commit. Good when you want to go hands-off. |
 
 **For existing projects:**
 
 | Command | What it does |
 |---|---|
 | `/plan {NAME}` | Capture brainstorming findings into a structured implementation plan. Good when you want to review before implementing. |
-| `/auto {NAME}` | Full autonomous loop — planning, implementation, validation, and commit. Good when you want to go hands-off. |
+| `/autopilot {NAME}` | Full autonomous loop — planning, implementation, validation, and commit. Good when you want to go hands-off. |
 
 Always present the relevant options and let the user choose how they want to proceed.
 

package/content/commands/showcase.md

@@ -49,7 +49,7 @@ If no references are provided, the agent will ask you to choose a style directio
 
 ### How It Integrates
 
-- In `/auto` or `/implement` — if the plan includes a landing page task, the showcase agent is used instead of the generic implement agent for that task
+- In `/autopilot` or `/implement` — if the plan includes a landing page task, the showcase agent is used instead of the generic implement agent for that task
 - In `/parallelize` — landing page work can be a dedicated stream using the showcase agent
 - Standalone — run `/showcase` directly to design a landing page from scratch or redesign an existing one
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@allthingsclaude/blueprints",
-  "version": "0.3.0-beta.25",
+  "version": "0.3.0-beta.26",
   "description": "Claude Code commands and agents for enhanced AI-assisted development workflows",
   "type": "module",
   "main": "dist/index.js",