Update documentation and rename references from DevOrch to devorch

guicheffer · claude · guicheffer · commit 8f08a201a92b · 2026-01-22T23:32:37.000+01:00
- Standardize project name to lowercase 'devorch' throughout docs
- Update changelog with recent changes
- Refine developer and user guides
- Improve handbook and playbook documentation
- Update CLI help text and menu system
- Adjust package.json and test snapshots

Co-Authored-By: Claude &lt;noreply@anthropic.com&gt;
diff --git a/docs/changelog.md b/docs/changelog.md
@@ -191,10 +191,10 @@ The v1.0.x series represents the rapid evolution of devorch from its initial rel
 
 #### Early Features (v1.0.1-87)
 - Simplify CLI for git-clone workflow
-- Rebrand from Agent OS to DevOrch
+- Rebrand from Agent OS to devorch
 - Add version source from GitHub releases
 - Add documentation links and table of contents to README
-- Add section for updating local DevOrch installation
+- Add section for updating local devorch installation
 - Reorganize documentation: prioritize embedded specs over polyrepo
 - Refactor polyrepo setup with various approaches
 - Improve git submodules handling
@@ -268,7 +268,7 @@ The v1.0.x series represents the rapid evolution of devorch from its initial rel
 - Documentation and setup guides
 
 ### Changed
-- Project rebranded from "Agent OS" to "DevOrch"
+- Project rebranded from "Agent OS" to "devorch"
 - Reorganized file structure with improved separation of concerns
 
 ### Fixed
diff --git a/docs/developer-guide/dev-guide.md b/docs/developer-guide/dev-guide.md
@@ -1,8 +1,8 @@
-# Developer's Guide to DevOrch
+# Developer's Guide to devorch
 
 ![Developer's Guide](../assets/dev-guide-header.jpg)
 
-A practical guide to using DevOrch with Claude Code for AI-powered development workflows.
+A practical guide to using devorch with Claude Code for AI-powered development workflows.
 
 ## Quick Start
 
diff --git a/docs/developer-guide/extending.md b/docs/developer-guide/extending.md
@@ -1,10 +1,10 @@
-# Extending DevOrch
+# Extending devorch
 
 Create custom commands, subagents, and skills for your project.
 
 ## Overview
 
-DevOrch can be extended with custom assets:
+devorch can be extended with custom assets:
 - **Commands:** Slash commands for workflows
 - **Subagents:** Specialized agents for focused tasks
 - **Skills:** Knowledge modules (Claude Code only, advanced)
diff --git a/docs/handbook/context-engineering.md b/docs/handbook/context-engineering.md
@@ -36,6 +36,6 @@ Every major artifact in our product development lifecycle is an act of context e
 
 * **For Product Managers:** You are the primary context engineers. When you create a `prd.md`, you are not just writing a document; you are building the foundational context container for the entire initiative. By synthesizing customer data, business goals, and problem statements into a structured format, you provide the "why" that guides every subsequent step.  
 * **For UX Designers:** Your `ux-spec.md` is an act of engineering user experience context. You translate abstract user needs and visual designs into a detailed, logical flow with clear rules and states. This structured documentation is what allows an AI to understand the intended interaction and generate code that reflects it.  
-* **For Engineers:** The `technical-spec.md` is the final and most crucial piece of context engineering. You synthesize the "what" and "why" from Product and the user flow from UX into a precise, unambiguous technical blueprint. Your team's **Context Training and Skills** in [DevOrch](https://github.com/guicheffer/devorch/) are a form of reusable, pre-packaged context, ensuring the AI consistently adheres to your team's standards.
+* **For Engineers:** The `technical-spec.md` is the final and most crucial piece of context engineering. You synthesize the "what" and "why" from Product and the user flow from UX into a precise, unambiguous technical blueprint. Your team's **Context Training and Skills** in [devorch](https://github.com/guicheffer/devorch/) are a form of reusable, pre-packaged context, ensuring the AI consistently adheres to your team's standards.
 
 Mastering the art of context engineering is the key to unlocking the full potential of our AI-native workflow. It is human skills that make the AI flow.
diff --git a/docs/handbook/dive-deeper/engineering-manager-playbook-em.md b/docs/handbook/dive-deeper/engineering-manager-playbook-em.md
@@ -10,7 +10,7 @@ Your objective is to maximize team velocity and predictability by managing **con
 
 ### Key tools and services
 
-* **DevOrch:** The primary framework your team uses for consistency.  
+* **devorch:** The primary framework your team uses for consistency.  
   * **Onboarding:** Familiarize yourself with the concept of Profiles. Your role is not to write them, but to empower your team to own their creation and maintenance. Grant your senior engineers access to the [devorch](https://github.com/guicheffer/devorch) repository.  
 * **Survey Tools (e.g., Google Forms)**: Standard tools for gathering weekly team feedback.  
 * **Onboarding**: Create a simple, anonymous weekly survey for your team.  
@@ -43,7 +43,7 @@ Your primary function is to ensure the continuous flow of high-quality, unambigu
 Your team's success depends on the consistent application of AI-native workflows.
 
 1. **Coach the "When" and "Why":** Guide your team on when to use Agentic Development for quick, tactical tasks versus Spec-Driven Development for larger, strategic features.  
-2. **Empower, Don't Prescribe:** Empower your senior engineers to own and evolve your team's Context Training in DevOrch. Your job is to ensure they have the time and support to maintain these crucial customizations.  
+2. **Empower, Don't Prescribe:** Empower your senior engineers to own and evolve your team's Context Training in devorch. Your job is to ensure they have the time and support to maintain these crucial customizations.  
 3. **Focus on Outcomes:** Measure what matters: sprint predictability, feature lead time, and team satisfaction.
 
 #### Workflow 3: Leveraging AI for Oversight
diff --git a/docs/handbook/dive-deeper/engineering-spec-feature-name.md b/docs/handbook/dive-deeper/engineering-spec-feature-name.md
@@ -40,7 +40,7 @@
 
 ## 5. Task Breakdown & Agent Assignment
 
-*This section breaks down the work into actionable tasks, assigning each to a specific Implementer and Verifier agent from the DevOrch profile.*
+*This section breaks down the work into actionable tasks, assigning each to a specific Implementer and Verifier agent from the devorch profile.*
 
 ---
 
diff --git a/docs/handbook/dive-deeper/onboarding.md b/docs/handbook/dive-deeper/onboarding.md
@@ -45,7 +45,7 @@ You don't need to master everything; just find one or two new tools or rituals t
 
 **Step 3: Try One New Thing.** You don't have to change everything at once. The best way to start is to pick one small thing and try it for a week.
 
-* **Engineers:** Try using **DevOrch** for your next task.  
+* **Engineers:** Try using **devorch** for your next task.  
 * **Product:** Try writing your next spec as a `prd.md` file.  
 * **UX:** Try structuring your next Figma file for better AI handoff.  
 * **Everyone:** Try the "Demo Daily" ritual.
diff --git a/docs/handbook/dive-deeper/ux-playbook-ux.md b/docs/handbook/dive-deeper/ux-playbook-ux.md
@@ -14,7 +14,7 @@ To create actionable, context-rich design specs that serve as a direct input for
   * **Onboarding**: Structure your Figma pages to mirror the steps of the user journey (e.g., Information, Cart & Review, Shipping, Payment). This makes it easier for both AI and engineers to locate and understand the relevant screens.  
 * **AI Assistants (Thought Partner)**: Use tools like **ChatGPT** or **Gemini** to brainstorm and capture key aspects of the user journey, such as user objectives, friction points, edge cases, and microcopy.  
 * **AI Assistants (Implementation)**: Use tools like **Cursor** or **Claude Code** to make small, targeted design changes directly in the codebase without needing an engineer.  
-  * **Onboarding**: Get access to the relevant code repositories and the team's DevOrch profile. This will allow you to use agentic commands (e.g., `@ui-implementer`) to make precise changes.  
+  * **Onboarding**: Get access to the relevant code repositories and the team's devorch profile. This will allow you to use agentic commands (e.g., `@ui-implementer`) to make precise changes.  
 * **Markdown**: The format for your primary deliverable, the `ux-spec.md` file.  
   * **Onboarding**: Learn to create structured markdown documents that clearly link out to your Figma files and related specs.
 
diff --git a/docs/index.md b/docs/index.md
@@ -1,8 +1,8 @@
-# DevOrch Documentation
+# devorch Documentation
 
 > **⚠️ PRE-ALPHA WARNING**
 >
-> DevOrch is currently in pre-alpha development and **not ready for production use**. Features are experimental, APIs may change without notice, and breaking changes are expected. Use at your own risk.
+> devorch is currently in pre-alpha development and **not ready for production use**. Features are experimental, APIs may change without notice, and breaking changes are expected. Use at your own risk.
 
 **Composable AI workflow automation** - Install custom subagents and slash commands for Claude Code.
 
@@ -13,15 +13,15 @@ Configure exactly which AI agents and commands you need for your project.
 ## 📖 Documentation
 
 ### [User Guide](user-guide/quickstart.md)
-Complete guides for using DevOrch in your projects:
+Complete guides for using devorch in your projects:
 - Installation and setup
 - Configuration
 - Commands and workflows
 - AWS Bedrock integration
 - Skills and context training
 
 ### [Developer Guide](developer-guide/development.md)
-Resources for contributing to DevOrch:
+Resources for contributing to devorch:
 - Development setup
 - Architecture
 - Creating custom commands and subagents
diff --git a/docs/user-guide/concepts.md b/docs/user-guide/concepts.md
@@ -2,7 +2,7 @@
 
 Understanding devorch's architecture and components.
 
-## What is DevOrch?
+## What is devorch?
 
 **Composable AI workflow automation** for Claude Code. Install exactly the commands, subagents, and skills you need for your project.
 
diff --git a/docs/user-guide/install.md b/docs/user-guide/install.md
@@ -1,6 +1,6 @@
 # Quick Install
 
-This guide is designed for non-technical users (PMs, UX designers) who want to install DevOrch on a fresh computer without developer tools.
+This guide is designed for non-technical users (PMs, UX designers) who want to install devorch on a fresh computer without developer tools.
 
 > **Windows Users:** See the [Windows Setup Guide](./windows-setup.md) for Windows-specific instructions.
 
@@ -63,7 +63,7 @@ The setup wizard will automatically:
 - ✅ Help you select a Claude model
 - ✅ Configure Claude Code settings
 
-That's it! You're ready to use DevOrch.
+That's it! You're ready to use devorch.
 
 ## Troubleshooting
 
diff --git a/docs/user-guide/polyrepo.md b/docs/user-guide/polyrepo.md
@@ -102,7 +102,7 @@ Create `.mcp.json` in specs repo root:
 
 See [Workflows](./workflows.md) for MCP server details.
 
-### 5. Install DevOrch
+### 5. Install devorch
 
 ```bash
 devorch install
diff --git a/docs/user-guide/quickstart.md b/docs/user-guide/quickstart.md
@@ -408,5 +408,5 @@ devorch debug-bedrock
 ## Getting Help
 
 - Run `devorch --help` for CLI help
-- Check [Working with DevOrch](./working-with-devorch.md) for detailed workflows
+- Check [Working with devorch](./working-with-devorch.md) for detailed workflows
 - Open an issue at [github.com/guicheffer/devorch](https://github.com/guicheffer/devorch)
diff --git a/docs/user-guide/workflows.md b/docs/user-guide/workflows.md
@@ -55,7 +55,7 @@ Add integration tests for the auth flow
 - New payment flow with verification
 - Multi-repo refactoring
 
-**Tools:** DevOrch commands (`/gather-requirements`, `/create-spec`, `/create-tasks`, `/implement-task`, `/implement-spec`)
+**Tools:** devorch commands (`/gather-requirements`, `/create-spec`, `/create-tasks`, `/implement-task`, `/implement-spec`)
 
 **Benefits:**
 - Consistent implementation across workspace
diff --git a/docs/user-guide/working-with-spec-machine.md b/docs/user-guide/working-with-spec-machine.md
@@ -1,8 +1,8 @@
-# Working with DevOrch
+# Working with devorch
 
 ## When to Use Spec-Driven Development
 
-DevOrch is for **larger chunks of work** - epics and features requiring careful planning and execution across multiple repositories.
+devorch is for **larger chunks of work** - epics and features requiring careful planning and execution across multiple repositories.
 
 ### The Development Spectrum
 
@@ -24,7 +24,7 @@ Vibe Coding ←────── Agentic Coding ←────── Spec-Driv
 
 **Spec-Driven Development** - Comprehensive, planned work
 - Example: User engagement feature across frontend and backend
-- Tools: DevOrch CLI with profiles and workflows
+- Tools: devorch CLI with profiles and workflows
 - Benefit: Consistent implementation and verification across workspace
 
 ---
@@ -70,7 +70,7 @@ See [Polyrepo Setup Guide](./polyrepo.md) for details.
 
 ## Getting Started
 
-### 1. Install DevOrch
+### 1. Install devorch
 
 ```bash
 cd /path/to/your-repository
@@ -218,7 +218,7 @@ Add tests for the auth flow
 ## Summary
 
 ### Setup
-1. Install DevOrch
+1. Install devorch
 2. Choose preset or configure manually
 3. Set up MCP servers (optional)
 
diff --git a/mkdocs.yml b/mkdocs.yml
@@ -1,4 +1,4 @@
-site_name: 'DevOrch'
+site_name: 'devorch'
 site_description: 'Composable AI workflow automation. Complete AI toolkit for AI Native PDLC'
 
 plugins:
@@ -17,7 +17,7 @@ nav:
       - Core Concepts: 'user-guide/concepts.md'
       - Configuration: 'user-guide/configuration.md'
       - Workflows: 'user-guide/workflows.md'
-      - Working with DevOrch: 'user-guide/working-with-devorch.md'
+      - Working with devorch: 'user-guide/working-with-devorch.md'
       - Command Reference: 'user-guide/command-reference.md'
       - Skills: 'user-guide/skills.md'
       - Context Training: 'user-guide/context-training.md'
diff --git a/package.json b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "devorch",
   "version": "2.1.0",
-  "description": "DevOrch - A CLI tool for composable AI workflow automation. Install custom subagents and commands for Claude Code.",
+  "description": "devorch - A CLI tool for composable AI workflow automation. Install custom subagents and commands for Claude Code.",
   "homepage": "https://devor.ch",
   "repository": {
     "type": "git",
diff --git a/src/cli/lib/cli/cli-modes.ts b/src/cli/lib/cli/cli-modes.ts
@@ -106,7 +106,7 @@ export async function runInteractiveMode(
       }
 
       if (command === 'exit') {
-        showOutro('Thanks for using DevOrch! 👋', 'green');
+        showOutro('Thanks for using devorch! 👋', 'green');
         return;
       }
 
diff --git a/src/cli/lib/cli/help.ts b/src/cli/lib/cli/help.ts
@@ -14,7 +14,7 @@ const LOGO = `
  */
 export function showHelp(version: string): void {
   console.log(colors.red(LOGO));
-  console.log(colors.bold('DevOrch CLI'));
+  console.log(colors.bold('devorch CLI'));
   console.log(colors.dim(`Version ${version}\n`));
   console.log('Usage:');
   console.log('  devorch              Start interactive menu');
diff --git a/src/cli/lib/cli/menu-system.ts b/src/cli/lib/cli/menu-system.ts
@@ -46,7 +46,7 @@ function commandsToMenuOptions(commands: CommandMetadata[]): MenuOption[] {
 export async function showMainMenu(version: string): Promise<string> {
   displayHeader(version);
 
-  clack.intro(colors.red('DevOrch CLI'));
+  clack.intro(colors.red('devorch CLI'));
   console.log(colors.dim('  Press Ctrl+C at any time to cancel and return to menu\n'));
 
   const category = await clack.select({
diff --git a/src/cli/lib/filesystem/paths.ts b/src/cli/lib/filesystem/paths.ts
@@ -64,7 +64,7 @@ export const INSTALL_PATHS = {
   /** Claude Code root directory */
   claudeRoot: () => '.claude',
 
-  /** DevOrch state root directory */
+  /** devorch state root directory */
   specMachineRoot: () => join('devorch', '.state'),
 
   /** State file */
diff --git a/src/utils/colors.ts b/src/utils/colors.ts
@@ -1,7 +1,7 @@
 import pc from 'picocolors';
 
 /**
- * DevOrch Brand Colors
+ * devorch Brand Colors
  *
  * The CLI uses a modern color palette with:
  * - Primary: Red (used for main branding, logo, buttons)
diff --git a/templates/context-engine/backend-go-microservice/implementation.md b/templates/context-engine/backend-go-microservice/implementation.md
@@ -388,7 +388,7 @@ All patterns are extracted from yourcompany/reward-wallet, a production microser
 - **91% tech stack coverage** of declared technologies
 - **100% of patterns** used in production
 
-## Integration with DevOrch
+## Integration with devorch
 
 ### Workflow Integration
 
diff --git a/templates/dev-tools/help/command.md b/templates/dev-tools/help/command.md
@@ -9,7 +9,7 @@ partials:
   setup: common/partials/commands/command-setup.md
 ---
 
-# DevOrch Help
+# devorch Help
 
 ## Purpose
 
@@ -38,7 +38,7 @@ gh api repos/guicheffer/devorch/contents/docs/user-guide/quickstart.md --jq '.co
 
 ### PHASE 1: Present Help Menu
 
-🔧 DevOrch Help
+🔧 devorch Help
 
 What would you like help with?
 
diff --git a/tests/evals/utils/project-utils.ts b/tests/evals/utils/project-utils.ts
@@ -144,7 +144,7 @@ export async function createTestProject(testName: string, config: TestConfig): P
   console.log('\n📁 Test Project Paths:');
   console.log(`  Project:      ${paths.projectDir}`);
   console.log(`  Claude:       ${paths.claudeDir}`);
-  console.log(`  DevOrch: ${paths.specMachineDir}`);
+  console.log(`  devorch: ${paths.specMachineDir}`);
   console.log(`  Config:       ${paths.configPath}\n`);
 
   return paths;
diff --git a/tests/snapshots/commands/__snapshots__/help.test.ts.snap b/tests/snapshots/commands/__snapshots__/help.test.ts.snap
@@ -9,7 +9,7 @@ dependencies:
   subagents: []
 ---
 
-# DevOrch Help
+# devorch Help
 
 ## Purpose
 
@@ -65,7 +65,7 @@ IF \`blocked\` == true:
 
 ### PHASE 1: Present Help Menu
 
-🔧 DevOrch Help
+🔧 devorch Help
 
 What would you like help with?
 
