@context-forge/cli 0.6.19 → 0.6.20

package/commands/cf/onboard.md

@@ -14,59 +14,45 @@ working directory.
 
 **MCP:** Call `project_list`. Scan results for a project whose `projectPath`
 matches the current directory.
-**CLI fallback:** Run `cf project list` and check the output.
+**CLI:** Run `cf project list` and check the output.
 
 - If a project exists at this path → skip to Step 3.
 - If no project exists → continue to Step 2.
 
 ## Step 2 — Create project
 
-Create a new Context Forge project.
+Ask the user what they'd like to name their project. If a project name argument
+was provided with the command, use that. If the user declines to choose, default
+to the current directory name.
 
-Before creating the project, ensure git is initialized in the current
-directory. If there is no `.git` directory, ask the user to run `git init`
-(or run it for them if you have Bash access).
+**Primary:** Run `cf init <name>` via the shell. This single command handles
+everything: git initialization, project registration, guide installation,
+command installation, and IDE setup. After `cf init` completes, skip to Step 3.
 
-**MCP:** Call `project_create` with:
-- `name`: Use the argument provided with this command, or the current directory
-  name, or ask the user what they'd like to call their project.
-- `projectPath`: The current working directory (absolute path).
-- `developmentPhase`: "Phase 1: Concept" (default — no need to specify).
+**Important:** Do not rely on environment context (like "Is a git repository")
+to determine git status — `cf init` checks the actual directory and handles
+git initialization itself.
 
-**CLI fallback:** Run `cf init <name>`. This handles project creation plus
-guide installation and IDE setup in one step — if using the CLI path, skip
-to Step 4 after init completes.
+**MCP fallback** (if shell access is unavailable):
+1. Call `project_create` with `name` and `projectPath` (the CWD).
+2. Call `guide_install` to install the AI Project Guide.
+Note: the MCP fallback cannot initialize git. If the directory is not a git
+repository, inform the user they need to run `git init` first.
 
-Confirm to the user: "Project created: {name}."
+## Step 3 — Transition to concept discussion
 
-## Step 3 — Check and install guides
-
-Verify the AI Project Guide is installed, and install it if missing.
-
-**MCP:** Call `guide_status`.
-- If `installed: true` → skip installation.
-- If `installed: false` → call `guide_install`.
-
-**CLI fallback:** Run `cf guides status`. If not installed, run
-`cf guides install`.
-
-Do not draw attention to this step unless installation fails. It's
-infrastructure the user doesn't need to think about.
-
-## Step 4 — Transition to concept discussion
-
-The project is set up. Now begin the Phase 1 (Concept) conversation.
+The project is set up. Now begin the Phase 0 (Concept) conversation.
 
 **MCP:** Call `context_build` to generate the concept-phase context prompt.
 Use the returned prompt as your working context to guide the conversation.
 
-**CLI fallback:** Run `cf build` and use the output as your working context.
+**CLI:** Run `cf build` and use the output as your working context.
 
 Begin by asking the user to describe what they want to build. Guide them
 through the concept exploration naturally — the context prompt provides the
 structure. The goal is a concept document at the end of this conversation.
 
-## Step 5 — Mention ongoing guidance
+## Step 4 — Mention ongoing guidance
 
 After the concept conversation concludes (or if the user wants to pause),
 mention: "You can run `cf next` (or `/cf:next`) anytime to see what to do
@@ -75,7 +61,7 @@ next. It adapts as your project progresses."
 ## Notes
 
 - If any MCP tool call fails, fall back to the CLI equivalent.
-- If the user already has a project but is in a later phase (not Phase 1),
+- If the user already has a project but is in a later phase (not Phase 0),
   acknowledge this and suggest `cf next` instead of starting a concept
   discussion.
 - Keep the conversation natural. This is onboarding, not a checklist.

package/dist/commands/build.js

@@ -35,7 +35,7 @@ export function registerBuildCommand(program) {
             if (opts.phase) {
                 const resolved = resolvePhaseValue(opts.phase);
                 if (!resolved) {
-                    process.stderr.write(`Warning: '${opts.phase}' is not a recognized phase. Use a number (1-7), name (implementation), or shorthand (P6).\n`);
+                    process.stderr.write(`Warning: '${opts.phase}' is not a recognized phase. Use a number (0-7), name (implementation), or shorthand (P6).\n`);
                 }
                 const phaseValue = resolved ?? opts.phase;
                 workingCopy.developmentPhase = phaseValue;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@context-forge/cli",
-  "version": "0.6.19",
+  "version": "0.6.20",
   "description": "CLI for Context Forge — terminal access to context assembly, project management, workflow navigation, and configuration",
   "type": "module",
   "main": "dist/index.js",
@@ -32,7 +32,7 @@
   "dependencies": {
     "chalk": "^5.4.1",
     "commander": "^13.1.0",
-    "@context-forge/core": "0.6.19"
+    "@context-forge/core": "0.6.20"
   },
   "devDependencies": {
     "@types/node": "^25.3.0",