work-kit-cli 0.2.3 → 0.2.4

package/cli/src/commands/init.ts

@@ -95,9 +95,10 @@ export function initCommand(options: {
   mode: "full" | "auto";
   description: string;
   classification?: Classification;
+  gated?: boolean;
   worktreeRoot?: string;
 }): Action {
-  const { mode, description, classification } = options;
+  const { mode, description, classification, gated } = options;
   const worktreeRoot = options.worktreeRoot || process.cwd();
 
   // Guard: don't overwrite existing state
@@ -156,6 +157,7 @@ export function initCommand(options: {
     branch,
     started: new Date().toISOString(),
     mode: modeLabel,
+    ...(gated && { gated: true }),
     ...(classification && { classification }),
     status: "in-progress",
     currentPhase: firstPhase,

package/cli/src/engine/transitions.test.ts

@@ -104,13 +104,25 @@ describe("determineNextStep", () => {
     assert.equal(step.subStage, "clarify");
   });
 
-  it("returns wait-for-user when current phase is complete", () => {
+  it("auto-proceeds to next phase by default when current phase is complete", () => {
     const state = makeState();
     state.currentPhase = "plan";
     for (const ss of Object.values(state.phases.plan.subStages)) {
       ss.status = "completed";
     }
     const step = determineNextStep(state);
+    assert.equal(step.type, "phase-boundary");
+    assert.equal(step.phase, "build");
+  });
+
+  it("returns wait-for-user when gated and current phase is complete", () => {
+    const state = makeState();
+    state.gated = true;
+    state.currentPhase = "plan";
+    for (const ss of Object.values(state.phases.plan.subStages)) {
+      ss.status = "completed";
+    }
+    const step = determineNextStep(state);
     assert.equal(step.type, "wait-for-user");
     assert.equal(step.phase, "build");
   });

package/cli/src/engine/transitions.ts

@@ -75,12 +75,16 @@ export function determineNextStep(state: WorkKitState): NextStep {
     for (const phase of remainingPhases) {
       const ps = state.phases[phase];
       if (ps.status !== "skipped") {
-        // Phase boundary — wait for user confirmation before crossing
-        return {
-          type: "wait-for-user",
-          phase,
-          message: `${currentPhase} phase complete. Ready to start ${phase}. Proceed?`,
-        };
+        if (state.gated) {
+          // Gated mode — wait for user confirmation before crossing
+          return {
+            type: "wait-for-user",
+            phase,
+            message: `${currentPhase} phase complete. Ready to start ${phase}. Proceed?`,
+          };
+        }
+        // Default — auto-proceed to next phase
+        return { type: "phase-boundary", phase, message: `${currentPhase} complete → starting ${phase}` };
       }
     }
 

package/cli/src/index.ts

@@ -39,6 +39,7 @@ program
   .requiredOption("--mode <mode>", "Workflow mode: full or auto")
   .requiredOption("--description <text>", "Description of the work")
   .option("--classification <type>", "Work classification (auto mode): bug-fix, small-change, refactor, feature, large-feature")
+  .option("--gated", "Wait for user approval between phases (default: auto-proceed)")
   .option("--worktree-root <path>", "Override worktree root directory")
   .action((opts) => {
     try {
@@ -46,6 +47,7 @@ program
         mode: opts.mode as "full" | "auto",
         description: opts.description,
         classification: opts.classification as Classification | undefined,
+        gated: opts.gated || false,
         worktreeRoot: opts.worktreeRoot,
       });
       console.log(JSON.stringify(result, null, 2));

package/cli/src/state/schema.ts

@@ -81,6 +81,7 @@ export interface WorkKitState {
   branch: string;
   started: string;
   mode: "full-kit" | "auto-kit";
+  gated?: boolean;
   classification?: Classification;
   status: "in-progress" | "paused" | "completed" | "failed";
   currentPhase: PhaseName | null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "work-kit-cli",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "description": "Structured development workflow for Claude Code. Two modes, 6 phases, 27 sub-stages.",
   "type": "module",
   "bin": {

package/skills/auto-kit/SKILL.md

@@ -97,6 +97,7 @@ The table is a guide, not a rigid rule. Adjust based on the actual request:
    cd worktrees/<slug>
    npx work-kit-cli init --mode auto --description "<description>" --classification <classification>
    ```
+   If the user requested gated mode (manual approval between phases), add `--gated`.
 2. Show the workflow to the user: `npx work-kit-cli workflow`
 3. User can adjust: `npx work-kit-cli workflow --add review/security` or `npx work-kit-cli workflow --remove test/e2e`
 4. **Wait for approval** — user can add/remove steps before proceeding
@@ -216,5 +217,5 @@ Run **Wrap-up** — read `.claude/skills/wk-wrap-up/SKILL.md` and follow its ins
 
 - **Always work inside the worktree directory** — `cd worktrees/<slug>` before running any commands
 - **Commit state after each phase boundary** — `git add .work-kit/ && git commit -m "work-kit: complete <phase>"`
-- **Human stays in control** — stop between phases, don't auto-proceed
+- **Auto-proceed by default** — phases flow continuously unless `--gated` was passed at init, in which case stop between phases for user approval
 - **One feature per session** — each session handles a single feature. To work on multiple features in parallel, use separate terminal sessions

package/skills/full-kit/SKILL.md

@@ -39,6 +39,7 @@ Do not proceed until `doctor` reports all checks passed.
    cd worktrees/<slug>
    npx work-kit-cli init --mode full --description "<description>"
    ```
+   If the user requested gated mode (manual approval between phases), add `--gated`.
 2. Parse the JSON response and follow the action
 3. Continue with the execution loop below
 
@@ -62,7 +63,7 @@ The CLI manages all state transitions, prerequisites, and loopbacks. Follow this
 3. Follow the action type:
    - **`spawn_agent`**: Use the Agent tool with the provided `agentPrompt`. Pass `skillFile` path for reference. After the agent completes: `npx work-kit-cli complete <phase>/<sub-stage> --outcome <outcome>`
    - **`spawn_parallel_agents`**: Spawn all agents in the `agents` array in parallel using the Agent tool. Wait for all to complete. Then spawn `thenSequential` if provided. After all complete: `npx work-kit-cli complete <onComplete target>`
-   - **`wait_for_user`**: Report the message to the user and stop. Wait for them to say "proceed" before running `npx work-kit-cli next` again.
+   - **`wait_for_user`**: Report the message to the user and stop. Wait for them to say "proceed" before running `npx work-kit-cli next` again. (Only appears in `--gated` mode.)
    - **`loopback`**: Report the loopback to the user, then run `npx work-kit-cli next` to continue from the target.
    - **`complete`**: Done — run wrap-up if not already done.
    - **`error`**: Report the error and suggestion to the user. Stop.
@@ -197,5 +198,5 @@ Run **Wrap-up** — read `.claude/skills/wk-wrap-up/SKILL.md` and follow its ins
 - **Always work inside the worktree directory** — `cd worktrees/<slug>` before running any commands
 - **Commit state after each phase** — `git add .work-kit/ && git commit -m "work-kit: complete <phase>"`
 - **Don't skip phases** — even if a phase seems unnecessary, run it and let it determine "nothing to do"
-- **Human stays in control** — stop between phases, don't auto-proceed
+- **Auto-proceed by default** — phases flow continuously unless `--gated` was passed at init, in which case stop between phases for user approval
 - **One feature per session** — each session handles a single feature. To work on multiple features in parallel, use separate terminal sessions