5-phase-workflow 1.9.4 → 2.0.0

package/src/commands/5/configure.md

@@ -1,53 +1,51 @@
 ---
 name: 5:configure
-description: Configures the project. Analyzes project, gathers preferences, writes config.json, and creates feature spec for remaining setup. Follow up with /5:plan-implementation CONFIGURE.
+description: Configures the project. Analyzes project, gathers preferences, writes config.json, and creates .5/features/CONFIGURE/plan.md. Follow up with /5:implement CONFIGURE.
 allowed-tools: Read, Write, Bash, Glob, Grep, AskUserQuestion
 user-invocable: true
-model: opus
-context: fork
 ---
 
 <role>
-You are a Project Configurator. You analyze a project, gather preferences, and write config.json plus a feature spec.
-You do NOT generate AGENTS.md, CLAUDE.md, documentation files, or skills directly — those are Phase 3's job.
-You write ONLY to: .5/config.json, .5/version.json, .5/features/CONFIGURE/feature.md, and .gitignore.
-After writing config.json and the feature spec, you are DONE. Exit immediately.
+You are a Project Configurator. You analyze a project, gather preferences, and write config.json plus a unified plan.
+You do NOT generate AGENTS.md, CLAUDE.md, documentation files, or skills directly — those are /5:implement's job.
+You write ONLY to: .5/config.json, .5/version.json, .5/features/CONFIGURE/plan.md, and .gitignore.
+After writing config.json and the unified plan, you are DONE. Exit immediately.
 </role>
 
-# Configure (Phase 1 - Plan Feature for Project Configuration)
+# Configure (Project Setup Plan)
+
+Current commit: !`git rev-parse --short HEAD 2>/dev/null || echo "none"`
 
 ## Overview
 
-This command is **Phase 1** of the 5-phase workflow applied to project configuration itself. It analyzes the project, asks the user questions, and outputs a feature spec at `.5/features/CONFIGURE/feature.md`.
+This command prepares project configuration. It analyzes the project, asks preference questions, writes `.5/config.json`, and writes a unified plan at `.5/features/CONFIGURE/plan.md`.
 
 After running this command, proceed through the standard phases:
-1. **`/5:configure`** (this command) - Plan the configuration feature
-2. `/5:plan-implementation CONFIGURE` - Create implementation plan
-3. `/5:implement-feature CONFIGURE` - Execute configuration (uses `configure-docs-index` and `configure-skills`)
-4. `/5:verify-implementation` - Verify configuration
-5. `/5:review-code` - Review generated files
+1. **`/5:configure`** (this command) - Create config and CONFIGURE plan
+2. `/5:implement CONFIGURE` - Execute configuration (uses `configure-docs-index` and `configure-skills`)
+3. `/5:review` - Review generated files if desired
 
 ## ⚠️ CRITICAL SCOPE CONSTRAINT
 
-**THIS COMMAND WRITES config.json AND CREATES THE FEATURE SPEC. NOTHING ELSE.**
+**THIS COMMAND WRITES config.json AND CREATES THE CONFIGURE PLAN. NOTHING ELSE.**
 
 Your job in this command:
 ✅ Analyze project (detect type, build commands, etc.)
 ✅ Gather user preferences via questions
 ✅ Write `.5/config.json` directly
-✅ Create feature spec at `.5/features/CONFIGURE/feature.md` for remaining work
-✅ Tell user to run /5:plan-implementation CONFIGURE
+✅ Create unified plan at `.5/features/CONFIGURE/plan.md` for remaining work
+✅ Tell user to run /5:implement CONFIGURE
 
 Your job is NOT:
-❌ Create AGENTS.md or CLAUDE.md directly (Phase 3 does this)
-❌ Generate documentation files directly (Phase 3 does this)
-❌ Generate skills directly (Phase 3 does this)
+❌ Create AGENTS.md or CLAUDE.md directly (/5:implement does this)
+❌ Generate documentation files directly (/5:implement does this)
+❌ Generate skills directly (/5:implement does this)
 ❌ Skip user interaction
 ❌ Assume project structure
 
-**After writing config.json, creating the feature spec, and informing the user, YOUR JOB IS COMPLETE. EXIT IMMEDIATELY.**
+**After writing config.json, creating the unified plan, and informing the user, YOUR JOB IS COMPLETE. EXIT IMMEDIATELY.**
 
-**If you find yourself creating AGENTS.md, CLAUDE.md, documentation files, or skills, STOP IMMEDIATELY. You should only be writing config.json and the feature spec.**
+**If you find yourself creating AGENTS.md, CLAUDE.md, documentation files, or skills, STOP IMMEDIATELY. You should only be writing config.json and the unified plan.**
 
 ## Configuration Process
 
@@ -94,7 +92,7 @@ fi
 
 **1e. Check AGENTS.md / CLAUDE.md:**
 - If `AGENTS.md` exists, read its content
-- If `AGENTS.md` does not exist but `CLAUDE.md` exists with real content (not just `@AGENTS.md`), read it — this is a legacy setup that will be migrated to AGENTS.md during Phase 3
+- If `AGENTS.md` does not exist but `CLAUDE.md` exists with real content (not just `@AGENTS.md`), read it — this is a legacy setup that will be migrated to AGENTS.md during planning
 
 **1f. Scan existing skills:**
 - Check `.claude/skills/` for existing project-specific skills
@@ -259,7 +257,7 @@ If no patterns/commands detected:
 - Allow manual entry of pattern names/locations or command names
 
 **2m. Git-ignore `.5/features/` folder:**
-- "The `.5/features/` folder will contain feature specs, implementation plans, and state files. Would you like to add it to `.gitignore`?"
+- "The `.5/features/` folder will contain unified plans, state files, and review findings. Would you like to add it to `.gitignore`?"
   - Options:
     1. "Yes, add to .gitignore (recommended)" — workflow artifacts stay local, not tracked in version control
     2. "No, track in git" — useful if you want to share specs and plans with your team
@@ -283,7 +281,7 @@ mkdir -p .5
 After writing config.json, update `.5/version.json` so the reconfigure reminder can track staleness:
 1. Read `.5/version.json` (if it exists)
 2. Set `configuredAt` to the current ISO timestamp (`new Date().toISOString()`)
-3. Set `configuredAtCommit` to the current short commit hash (run `git rev-parse --short HEAD`)
+3. Set `configuredAtCommit` to the current short commit hash injected at the top of this command
 4. Write back `.5/version.json` preserving all other fields
 
 **Apply `.gitignore` if selected:**
@@ -300,20 +298,89 @@ Ensure `.5/.reconfig-reminder` is gitignored (it's a transient runtime flag that
 1. Check if `.gitignore` exists in the project root — create it if not
 2. Check if `.5/.reconfig-reminder` is already listed — if not, append `.5/.reconfig-reminder` on a new line
 
-### Step 3: Create Feature Spec
+### Step 3: Create Configuration Plan
 
-Write `.5/features/CONFIGURE/feature.md` containing all gathered data:
+Write `.5/features/CONFIGURE/plan.md` containing all gathered data:
 
 ```markdown
-# Feature: Project Configuration
+---
+ticket: CONFIGURE
+feature: CONFIGURE
+created: {ISO-timestamp}
+---
+
+# Plan: CONFIGURE - Project Configuration
 
-## Summary
+## Overview
 Generates AGENTS.md, CLAUDE.md shim, a rebuildable codebase index, and project-specific skills. (config.json already written.)
 
-## Requirements
+## What Changes
+
+- Generate focused documentation and a rebuildable codebase index.
+- Generate selected project-specific skills and scoped rules.
+- Preserve existing user-authored AGENTS.md/CLAUDE.md content.
+
+## Existing Patterns to Follow
+
+- `.claude/skills/configure-docs-index/SKILL.md` - documentation and index generation behavior.
+- `.claude/skills/configure-skills/SKILL.md` - skill and rule generation behavior.
+
+## Constraints
+
+- config.json is already written by `/5:configure`.
+- Do not generate empty placeholder documentation or index files.
+- Preserve user-authored sections in AGENTS.md.
+
+## Scope
+
+### In
+
+- Documentation files under `.5/`.
+- `.5/index/` and rebuild script.
+- AGENTS.md plus CLAUDE.md shim.
+- Selected create/run skills.
+- Selected scoped rules.
 
-### Requirement 1: Generate Documentation Files
-Handled by: `configure-docs-index`
+### Out
+
+- Changing preferences already saved in `.5/config.json`.
+
+## Acceptance Criteria
+
+- [ ] `.5/ARCHITECTURE.md` exists when architecture knowledge was found.
+- [ ] `.5/TESTING.md` exists when test knowledge was found.
+- [ ] `.5/CONCERNS.md` exists only if concerns were found.
+- [ ] `.5/index/rebuild-index.sh` exists and rebuilds the index.
+- [ ] `.5/index/README.md` documents generated index files.
+- [ ] `AGENTS.md` references created `.5/` files and the index rebuild rule.
+- [ ] `CLAUDE.md` contains only `@AGENTS.md`.
+- [ ] Selected project-specific skills are generated in `.claude/skills/`.
+- [ ] Selected scoped rules are generated in `.claude/rules/`.
+- [ ] User-written AGENTS.md/CLAUDE.md content is preserved.
+
+## Decisions
+
+- [DECIDED] Use the detected project type, build command, test command, ticket settings, review tool, and selected patterns from this configure session.
+- [FLEXIBLE] Omit optional generated files when no useful project knowledge exists.
+- [DEFERRED] Further preference changes; rerun `/5:configure` for those.
+
+## Module Impact
+
+| Module/Area | Impact |
+|-------------|--------|
+| `.5/` | Create/update documentation and index artifacts. |
+| `AGENTS.md` / `CLAUDE.md` | Create or update provider instructions. |
+| `.claude/skills/` | Create selected project-specific skills. |
+| `.claude/rules/` | Create selected scoped rules. |
+
+## Component Checklist
+
+| Component | Action | Target Path | Intent |
+|-----------|--------|-------------|--------|
+| configure docs and index | create | `.5/` | Generate project documentation, codebase index, AGENTS.md, and CLAUDE.md shim. |
+| configure skills and rules | create | `.claude/skills/` | Generate selected create/run skills and scoped rules from detected conventions. |
+
+## Technical Notes
 
 Analyze the codebase and generate focused documentation capturing only non-derivable knowledge (skip version numbers, dependency lists, directory layouts, linter configs — Claude Code can look these up directly):
 
@@ -330,24 +397,13 @@ Analyze the codebase and generate focused documentation capturing only non-deriv
 - Re-running the script should fully refresh the index in place
 
 **Create AGENTS.md** (provider-agnostic instructions file):
-- Project overview and build commands
-- Links to whichever `.5/` documentation files were created
-- Links to `.5/index/README.md`, the generated index files, and `.5/index/rebuild-index.sh`
-- An explicit instruction that if the codebase index is older than one day, it should be regenerated by running `.5/index/rebuild-index.sh`
-- Workflow rules section (verbatim):
-  ```
-  ## Workflow Rules
-  When running `/5:` workflow commands, follow the command instructions exactly as written.
-  Do not skip steps, combine phases, or proceed to actions not specified in the current command.
-  Each phase produces a specific artifact — do not create artifacts belonging to other phases.
-  ```
-- Mandatory coding guidelines:
-  1. Types should be clear and types should be available when possible
-  2. Use doc (jsdoc, javadoc, pydoc, etc) concisely. No doc is better than meaningless doc
-  3. Keep files short and structured
-  4. Extract methods, classes
-  5. Respect SRP and DRY
-  6. Make code maintainable and modular
+- Use `.claude/templates/AGENTS.md` as the source template
+- Fill `{PROJECT_OVERVIEW}` with 1-2 sentences from README/package.json
+- Fill `{BUILD_RUN_COMMANDS}` with build, test, and other detected commands
+- Fill `{PROJECT_DOCUMENTATION_LINKS}` with whichever `.5/` documentation files were created
+- Fill `{CODEBASE_INDEX_LINKS}` with `.5/index/README.md`, generated index files, and `.5/index/rebuild-index.sh`
+- Fill `{CUSTOM_DOCUMENTATION}` with preserved user-authored sections under `## Custom Documentation`; remove the placeholder if there is no custom content
+- Preserve static template sections exactly as written, including skill usage, workflow rules, coding guidelines, simplicity, testing, surgical changes, goal-driven execution, and index freshness
 
 **Create CLAUDE.md shim:**
 - Contains only `@AGENTS.md` (Claude Code include syntax)
@@ -382,43 +438,23 @@ Only generate rules for patterns that were actually detected:
 - `api-patterns.md` — API conventions, error handling (scoped to API/route/controller files)
 - `dependencies.md` — dependency usage patterns, env var conventions (unconditional)
 
-## Acceptance Criteria
-- [ ] `.5/` directory created
-- [ ] Documentation files exist and contain only non-derivable knowledge:
-  - [ ] `.5/ARCHITECTURE.md` — architecture, conventions, where to add code
-  - [ ] `.5/TESTING.md` — test patterns and gotchas
-  - [ ] `.5/CONCERNS.md` — only if concerns were found (omit if empty)
-- [ ] `.5/index/` directory exists
-- [ ] `.5/index/rebuild-index.sh` exists and rebuilds the index
-- [ ] `.5/index/README.md` exists and documents the generated index files
-- [ ] Multiple focused `.5/index/*.md` files are generated for applicable codebase concerns
-- [ ] Empty sections omitted (no "Not detected" / "None found" placeholders)
-- [ ] `AGENTS.md` exists with references to created `.5/` files
-- [ ] `AGENTS.md` links to the codebase index and rebuild script
-- [ ] `AGENTS.md` says to regenerate the index if it is older than one day
-- [ ] `AGENTS.md` contains 6 coding guidelines
-- [ ] `CLAUDE.md` exists and contains only `@AGENTS.md`
-- [ ] All specified project-specific skills are generated in `.claude/skills/`
-- [ ] Generated skills reference actual project conventions
-- [ ] If AGENTS.md or CLAUDE.md existed before, user-written sections are preserved in AGENTS.md
-- [ ] `.claude/rules/` directory exists with scoped rule files (if rules generation selected)
-- [ ] Generated rules use `paths:` frontmatter for scoping where applicable
-- [ ] Rules contain concise directives, not documentation
-- [ ] No rules generated for undetected patterns
+## Next Steps
+
+1. Run `/5:implement CONFIGURE`.
 ```
 
-**Important:** Use `mkdir -p .5/features/CONFIGURE` before writing the feature spec.
+**Important:** Use `mkdir -p .5/features/CONFIGURE` before writing the unified plan.
 
 ### Step 4: Guide User to Next Phase
 
 Tell the user:
 
 1. "Configuration saved to `.5/config.json`"
-2. "Configuration feature planned at `.5/features/CONFIGURE/feature.md`"
+2. "Configuration plan written to `.5/features/CONFIGURE/plan.md`"
 3. "Next steps:"
    - "Run `/clear` to reset context"
-   - "Then run `/5:plan-implementation CONFIGURE`"
-4. "After that: Continue with `/5:implement-feature CONFIGURE` -> `/5:verify-implementation` -> `/5:review-code` (clearing context between each phase)"
+   - "Then run `/5:implement CONFIGURE`"
+4. "After that: Run `/5:review` if you want a review of generated files"
 
 ## Related Documentation
 - [configure-docs-index skill](../../skills/configure-docs-index/SKILL.md)

package/src/commands/5/discuss-feature.md

@@ -1,53 +1,45 @@
 ---
 name: 5:discuss-feature
-description: Discusses and refines an existing feature specification through iterative Q&A. Use after /plan-feature when requirements need clarification or changes. Updates the feature spec based on discussion.
+description: Discusses and refines an existing unified plan through iterative Q&A. Use after /5:plan when requirements need clarification or changes. Updates the unified plan based on discussion.
 allowed-tools: Read, Write, Glob, Grep, Agent, AskUserQuestion
 user-invocable: true
-model: opus
 context: inherit
 ---
 
 <role>
-You are a Feature Discussion Facilitator. You refine existing feature specifications through Q&A.
-You do NOT create new feature specs, create implementation plans, write code, or start implementation.
-You read an existing feature.md, discuss it with the user, and update only the changed sections.
-After updating the spec and informing the user, you are DONE.
+You are a Feature Discussion Facilitator. You refine existing unified plans through Q&A.
+You do NOT create new unified plans, create implementation plans, write code, or start implementation.
+You read an existing plan.md, discuss it with the user, and update only the changed sections.
+After updating the plan and informing the user, you are DONE.
 </role>
 
-# Discuss Feature Specification (Phase 1 - Optional Iteration)
+# Discuss Feature Plan (Optional Iteration)
 
 ## Overview
 
-This skill is part of **Phase 1** (Feature Planning) of the 5-phase workflow:
-1. **Feature Planning** - Initial requirements gathering (`/plan-feature`), then optional iteration (`/discuss-feature`)
-2. **Implementation Planning** - Map to technical components
-3. **Orchestrated Implementation** - Execute with state tracking
-4. **Verify Implementation** - Check completeness and correctness
-5. **Code Review** - Apply automated quality improvements
+This helper refines the unified `plan.md` created by `/5:plan`.
 
-This skill enables **optional iterative refinement** of feature specs after initial planning through discussion, clarification, and requirement changes. Use it when the initial spec needs adjustments before proceeding to implementation planning.
+Use it when requirements, scope, acceptance criteria, decisions, or the component checklist need adjustment before `/5:implement`.
 
 ## ⚠️ CRITICAL SCOPE CONSTRAINT
 
-**THIS COMMAND ONLY UPDATES FEATURE SPECIFICATIONS. IT DOES NOT PLAN OR IMPLEMENT.**
+**THIS COMMAND ONLY UPDATES THE UNIFIED PLAN. IT DOES NOT IMPLEMENT.**
 
 Your job in this command:
-✅ Read existing feature specification
+✅ Read existing unified plan
 ✅ Ask what user wants to discuss
 ✅ Explore codebase if needed for context
 ✅ Ask clarifying questions
-✅ Update feature specification
-✅ Tell user to run /5:plan-implementation
+✅ Update unified plan
+✅ Tell user to run /5:implement
 
 Your job is NOT:
-❌ Create new feature specs (use /5:plan-feature)
-❌ Create implementation plans
-❌ Map to technical components
+❌ Create new unified plans (use /5:plan)
 ❌ Start implementation
 ❌ Write any code
-❌ Rewrite entire feature spec (only update changed sections)
+❌ Rewrite entire unified plan (only update changed sections)
 
-**After updating the feature spec and informing the user, YOUR JOB IS COMPLETE. EXIT IMMEDIATELY.**
+**After updating the unified plan and informing the user, YOUR JOB IS COMPLETE. EXIT IMMEDIATELY.**
 
 ## Use Cases
 
@@ -63,36 +55,38 @@ Use this skill when:
 ## Prerequisites
 
 Before invoking this skill, ensure:
-1. Feature spec exists at `.5/features/{feature-name}/feature.md`
+1. Unified plan exists at `.5/features/{feature-name}/plan.md`
 2. You have the feature name or ticket ID ready (e.g., "PROJ-1234-add-feature")
 
 ## Discussion Process
 
 ### Step 1: Extract Feature Name
 
-If user provides only ticket ID (e.g., "PROJ-1234"), find the feature file:
-- Use Glob: `.5/features/{TICKET-ID}-*/feature.md` (pattern from config)
+If user provides only ticket ID (e.g., "PROJ-1234"), find the plan file:
+- Use Glob: `.5/features/{TICKET-ID}-*/plan.md` (pattern from config)
 - Match the ticket ID
 - If multiple matches, ask user to specify
-- If no match found, inform user and suggest running `/plan-feature` first
+- If no match found, inform user and suggest running `/5:plan` first
 
 If user provides full feature name (e.g., "PROJ-1234-add-feature"), use directly.
 
-### Step 2: Read Feature Specification
+### Step 2: Read Plan
 
-Read the feature spec from `.5/features/{feature-name}/feature.md`.
+Read the unified plan from `.5/features/{feature-name}/plan.md`.
 
 Extract current state:
 - Ticket ID
-- Summary
-- Requirements (functional and non-functional)
+- Overview
+- What Changes
+- Existing Patterns to Follow
 - Constraints
-- Affected domains
-- Entity definitions
-- Business rules
-- Acceptance criteria
-- Alternatives considered
-- Decisions (with [DECIDED]/[FLEXIBLE]/[DEFERRED] labels)
+- Scope
+- Acceptance Criteria
+- Decisions ([DECIDED]/[FLEXIBLE]/[DEFERRED])
+- Module Impact
+- Component Checklist
+- Technical Notes
+- Alternatives Considered
 
 ### Step 3: Initial Discussion Prompt
 
@@ -135,7 +129,7 @@ Use Agent tool with subagent_type=Explore for complex exploration.
 
 Based on the discussion topic, ask targeted follow-up questions using AskUserQuestion.
 
-Ask targeted follow-up questions informed by the feature spec and any codebase exploration. Focus on: requirements clarity, scope boundaries, edge cases, technical constraints, and acceptance criteria. Challenge assumptions constructively — suggest simpler alternatives when appropriate.
+Ask targeted follow-up questions informed by the unified plan and any codebase exploration. Focus on: requirements clarity, scope boundaries, edge cases, technical constraints, and acceptance criteria. Challenge assumptions constructively — suggest simpler alternatives when appropriate.
 
 ### Step 6: Iterative Refinement
 
@@ -145,26 +139,24 @@ After each round of Q&A:
 3. Provide options:
    - "Yes, discuss another aspect"
    - "Yes, continue this topic"
-   - "No, update the spec"
+   - "No, update the plan"
 
 Allow multiple rounds of discussion until user is satisfied.
 
-### Step 7: Update Feature Specification
+### Step 7: Update Plan
 
-When user indicates they're done discussing, update `.5/features/{feature-name}/feature.md`:
+When user indicates they're done discussing, update `.5/features/{feature-name}/plan.md`:
 
 **Update these sections based on discussion:**
 
-1. **Summary** - If core understanding changed
-2. **Problem Statement** - If motivation clarified
-3. **Requirements** - Add/modify/remove based on discussion
-4. **Constraints** - Add new constraints discovered
-5. **Affected Domains** - If scope changed
-6. **Entity/Component Definitions** - If data model changed
-7. **Business Rules** - If logic clarified
-8. **Acceptance Criteria** - Add/refine verification criteria
-9. **Alternatives Considered** - Document discussed alternatives
-10. **Decisions** - Append new decisions from this session, tagged [DECIDED], [FLEXIBLE], or [DEFERRED] using Context/Decision format
+1. **Overview** - If core understanding changed
+2. **What Changes** - Add/modify/remove behavior
+3. **Constraints** - Add new constraints discovered
+4. **Scope** - If boundaries changed
+5. **Acceptance Criteria** - Add/refine verification criteria
+6. **Decisions** - Append new decisions tagged [DECIDED], [FLEXIBLE], or [DEFERRED]
+7. **Component Checklist** - Adjust components only when scope or requirements changed
+8. **Technical Notes / Alternatives Considered** - Document useful context from discussion
 
 **Preserve existing content** - Only update sections that changed during discussion.
 
@@ -184,16 +176,14 @@ When user indicates they're done discussing, update `.5/features/{feature-name}/
 
 ### Step 8: Inform Developer
 
-After updating the spec, tell the developer:
+After updating the plan, tell the developer:
 
-1. "Feature specification updated at `.5/features/{feature-name}/feature.md`"
+1. "Plan updated at `.5/features/{feature-name}/plan.md`"
 2. Summarize key changes:
    - "Added: {X}"
    - "Modified: {Y}"
    - "Removed: {Z}"
 3. Ask: "Would you like to:"
    - "Discuss more (run /5:discuss-feature again)"
-   - "Proceed to implementation planning (run `/clear` followed by `/5:plan-implementation {feature-name}`)"
-   - "Review the updated spec first"
-
-
+   - "Proceed to implementation (run `/clear` followed by `/5:implement {feature-name}`)"
+   - "Review the updated plan first"

package/src/commands/5/eject.md

@@ -3,6 +3,7 @@ name: 5:eject
 description: Eject from the update mechanism — permanently removes update infrastructure
 allowed-tools: Bash, Read, Edit, AskUserQuestion
 user-invocable: true
+context: inherit
 ---
 
 <role>
@@ -26,11 +27,11 @@ Ejecting permanently removes the update system from this installation. After eje
 
 All other workflow files (commands, skills, hooks, templates) remain untouched.
 
-**This is irreversible.** To restore update functionality, reinstall with `npx 5-phase-workflow`.
+**This is irreversible.** To restore update functionality, reinstall with `npx foifi`.
 
 ## Step 1: Check Current State
 
-Read `.5/version.json`. If it doesn't exist, tell the user: "No 5-Phase Workflow installation found (or already ejected)." and stop.
+Read `.5/version.json`. If it doesn't exist, tell the user: "No dev-workflow installation found (or already ejected)." and stop.
 
 Note the `packageVersion` for the confirmation message.
 
@@ -38,7 +39,7 @@ Note the `packageVersion` for the confirmation message.
 
 Tell the user what ejecting means:
 
-> **Eject from 5-Phase Workflow updates?**
+> **Eject from dev-workflow updates?**
 >
 > This will permanently delete:
 > - `.5/version.json` (version tracking)
@@ -55,7 +56,7 @@ Tell the user what ejecting means:
 > - `.codex/skills/5-eject/` (this skill)
 > - `.codex/instructions.md` is removed only if it is workflow-managed and no longer needed for remaining installed workflow files
 >
-> All other workflow files remain untouched. To restore updates later, reinstall with `npx 5-phase-workflow`.
+> All other workflow files remain untouched. To restore updates later, reinstall with `npx foifi`.
 
 Ask: "Proceed with eject?"
 
@@ -105,6 +106,6 @@ Tell the user:
 
 > Ejected successfully. Update infrastructure has been removed from this installation (was v{packageVersion}).
 >
-> To restore update functionality, reinstall with: `npx 5-phase-workflow`
+> To restore update functionality, reinstall with: `npx foifi`
 >
-> If this was a Codex install, use: `npx 5-phase-workflow --codex`
+> If this was a Codex install, use: `npx foifi --codex`