aiblueprint-cli 1.4.42 → 1.4.44

package/claude-code-config/skills/apex/steps/step-04-validate.md

@@ -1,8 +1,8 @@
 ---
 name: step-04-validate
-description: Self-check - run tests, verify AC, audit implementation quality
+description: Self-check - run tests, verify AC, audit implementation quality, complete workflow
 prev_step: steps/step-03-execute.md
-next_step: steps/step-05-examine.md
+next_step: null
 ---
 
 # Step 4: Validate (Self-Check)
@@ -27,11 +27,10 @@ next_step: steps/step-05-examine.md
 
 ## CONTEXT BOUNDARIES:
 
-- Implementation from step-03 (or step-03-execute-teams) is complete
+- Implementation from step-03 is complete
 - Tests may or may not pass yet
 - Type errors may exist
 - Focus is on verification, not new implementation
-- **If `{teams_mode}` = true:** The agent team is still alive. Do NOT shutdown or dismiss teammates. Team shutdown happens in step-09-finish only.
 
 ## YOUR TASK:
 
@@ -49,8 +48,7 @@ From previous steps:
 | `{acceptance_criteria}` | Success criteria |
 | `{auto_mode}` | Skip confirmations |
 | `{save_mode}` | Save outputs to files |
-| `{test_mode}` | Include test steps |
-| `{examine_mode}` | Auto-proceed to review |
+| `{economy_mode}` | No subagents mode |
 | `{output_dir}` | Path to output (if save_mode) |
 | Implementation | Completed in step-03 |
 </available_state>
@@ -172,38 +170,28 @@ Both MUST pass.
 **Summary:** All checks passing, ready for next step.
 ```
 
-### 8. Determine Next Step
+### 8. Complete Workflow
 
-**Decision tree:**
+**Show final summary:**
 
 ```
-IF {test_mode} = true:
-    → Load step-07-tests.md (test analysis and creation)
+✅ APEX Workflow Complete
 
-ELSE IF {examine_mode} = true:
-    → Load step-05-examine.md (adversarial review)
+**Task:** {task_description}
+**Task ID:** {task_id}
 
-ELSE IF {auto_mode} = false:
-    → Ask user:
-```
+**Validation Results:**
+- Typecheck: ✓ Passed
+- Lint: ✓ Passed
+- Tests: ✓ Passed
 
-```yaml
-questions:
-  - header: "Next"
-    question: "Validation complete. What would you like to do?"
-    options:
-      - label: "Run adversarial review"
-        description: "Deep review for security, logic, and quality"
-      - label: "Complete workflow"
-        description: "Skip review and finalize"
-      - label: "Add tests"
-        description: "Create additional tests first"
-    multiSelect: false
-```
+**Acceptance Criteria:**
+- [✓] AC1: Verified
+- [✓] AC2: Verified
 
-```
-ELSE:
-    → Complete workflow (show final summary)
+**Files Modified:** {list}
+
+🎉 Implementation complete and validated!
 ```
 
 ### 9. Complete Save Output (if save_mode)
@@ -218,10 +206,12 @@ Append to `{output_dir}/04-validate.md`:
 **Typecheck:** ✓
 **Lint:** ✓
 **Tests:** ✓
-**Next:** {next step based on flags}
+**Workflow:** Complete
 **Timestamp:** {ISO timestamp}
 ```
 
+Run: `bash {skill_dir}/scripts/update-progress.sh "{task_id}" "04" "validate" "complete"`
+
 ---
 
 ## SUCCESS METRICS:
@@ -232,6 +222,7 @@ Append to `{output_dir}/04-validate.md`:
 ✅ All AC verified
 ✅ Code formatted
 ✅ User informed of status
+✅ Workflow completed
 
 ## FAILURE MODES:
 
@@ -240,7 +231,6 @@ Append to `{output_dir}/04-validate.md`:
 ❌ Skipping tests for modified code
 ❌ Missing AC verification
 ❌ Proceeding with failures
-❌ **CRITICAL**: Not using AskUserQuestion for next step
 
 ## VALIDATION PROTOCOLS:
 
@@ -252,15 +242,10 @@ Append to `{output_dir}/04-validate.md`:
 
 ---
 
-## NEXT STEP:
+## WORKFLOW COMPLETE
 
-Based on flags (check in order):
-- **If test_mode:** Load `./step-07-tests.md`
-- **If examine_mode OR user requests:** Load `./step-05-examine.md`
-- **If pr_mode:** Load `./step-09-finish.md` to create pull request
-- **Otherwise:** Workflow complete - show summary
+This is the final step. After validation passes, the APEX workflow is complete.
 
 <critical>
-Remember: NEVER proceed with failing checks - fix everything first!
-If teams_mode is active: NEVER shutdown teammates — they stay alive until step-09-finish!
+Remember: NEVER claim completion with failing checks - fix everything first!
 </critical>

package/claude-code-config/skills/apex/templates/00-context.md

@@ -10,14 +10,10 @@
 | Flag | Value |
 |------|-------|
 | Auto mode (`-a`) | {{auto_mode}} |
-| Examine mode (`-x`) | {{examine_mode}} |
 | Save mode (`-s`) | {{save_mode}} |
-| Test mode (`-t`) | {{test_mode}} |
 | Economy mode (`-e`) | {{economy_mode}} |
 | Branch mode (`-b`) | {{branch_mode}} |
-| PR mode (`-pr`) | {{pr_mode}} |
 | Interactive mode (`-i`) | {{interactive_mode}} |
-| Tasks mode (`-k`) | {{tasks_mode}} |
 | Branch name | {{branch_name}} |
 
 ---
@@ -43,11 +39,5 @@ _To be defined in step-01-analyze.md_
 | 00-init | ⏸ Pending | |
 | 01-analyze | ⏸ Pending | |
 | 02-plan | ⏸ Pending | |
-| 02b-tasks | {{tasks_status}} | |
 | 03-execute | ⏸ Pending | |
 | 04-validate | ⏸ Pending | |
-| 05-examine | {{examine_status}} | |
-| 06-resolve | {{examine_status}} | |
-| 07-tests | {{test_status}} | |
-| 08-run-tests | {{test_status}} | |
-| 09-finish | {{pr_status}} | |

package/claude-code-config/skills/apex/templates/README.md

@@ -12,12 +12,7 @@ This directory contains template files used to initialize APEX workflow outputs
 | `01-analyze.md` | Analysis findings | Always (if save_mode) |
 | `02-plan.md` | Implementation plan | Always (if save_mode) |
 | `03-execute.md` | Implementation log | Always (if save_mode) |
-| `04-validate.md` | Validation results | Always (if save_mode) |
-| `05-examine.md` | Adversarial review findings | Only if examine_mode enabled |
-| `06-resolve.md` | Finding resolution log | Only if examine_mode enabled |
-| `07-tests.md` | Test analysis and creation | Only if test_mode enabled |
-| `08-run-tests.md` | Test runner log | Only if test_mode enabled |
-| `09-finish.md` | PR creation log | Only if pr_mode enabled |
+| `04-validate.md` | Validation results and workflow completion | Always (if save_mode) |
 | `step-complete.md` | Completion marker template | Referenced in steps |
 
 ## Template Variables
@@ -30,18 +25,12 @@ Templates use `{{variable}}` syntax for placeholders:
 | `{{task_description}}` | Plain text task description | `add authentication middleware` |
 | `{{timestamp}}` | ISO 8601 timestamp | `2026-01-12T10:30:00Z` |
 | `{{auto_mode}}` | Auto mode flag | `true` or `false` |
-| `{{examine_mode}}` | Examine mode flag | `true` or `false` |
 | `{{save_mode}}` | Save mode flag | `true` or `false` |
-| `{{test_mode}}` | Test mode flag | `true` or `false` |
 | `{{economy_mode}}` | Economy mode flag | `true` or `false` |
 | `{{branch_mode}}` | Branch mode flag | `true` or `false` |
-| `{{pr_mode}}` | PR mode flag | `true` or `false` |
 | `{{interactive_mode}}` | Interactive mode flag | `true` or `false` |
 | `{{branch_name}}` | Git branch name | `feature/add-auth` |
 | `{{original_input}}` | Raw user input | `/apex -a -s add auth` |
-| `{{examine_status}}` | Progress status for examine steps | `⏸ Pending` or `⏭ Skip` |
-| `{{test_status}}` | Progress status for test steps | `⏸ Pending` or `⏭ Skip` |
-| `{{pr_status}}` | Progress status for PR step | `⏸ Pending` or `⏭ Skip` |
 
 ## Setup Script
 
@@ -52,15 +41,12 @@ Initializes all template files in the output directory with variables replaced.
 **Usage:**
 ```bash
 bash scripts/setup-templates.sh \
-  "task_id" \
+  "feature_name" \
   "task_description" \
   "auto_mode" \
-  "examine_mode" \
   "save_mode" \
-  "test_mode" \
   "economy_mode" \
   "branch_mode" \
-  "pr_mode" \
   "interactive_mode" \
   "branch_name" \
   "original_input"
@@ -73,12 +59,7 @@ bash scripts/setup-templates.sh \
 ├── 01-analyze.md      # Always created
 ├── 02-plan.md         # Always created
 ├── 03-execute.md      # Always created
-├── 04-validate.md     # Always created
-├── 05-examine.md      # Only if examine_mode
-├── 06-resolve.md      # Only if examine_mode
-├── 07-tests.md        # Only if test_mode
-├── 08-run-tests.md    # Only if test_mode
-└── 09-finish.md       # Only if pr_mode
+└── 04-validate.md     # Always created
 ```
 
 ## Progress Update Script
@@ -137,7 +118,7 @@ Update `00-context.md` progress:
 ```
 ```
 
-**Token cost per step:** ~200 tokens × 9 steps = ~1,800 tokens
+**Token cost per step:** ~200 tokens × 5 steps = ~1,000 tokens
 
 ### After Optimization
 
@@ -158,9 +139,9 @@ bash {skill_dir}/scripts/update-progress.sh "{task_id}" "01" "analyze" "in_progr
 Append your findings to `01-analyze.md` as you work.
 ```
 
-**Token cost per step:** ~50 tokens × 9 steps = ~450 tokens
+**Token cost per step:** ~50 tokens × 5 steps = ~250 tokens
 
-**Total savings:** ~1,350 tokens per workflow execution (75% reduction)
+**Total savings:** ~750 tokens per workflow execution (75% reduction)
 
 ## How It Works
 

package/dist/cli.js

@@ -33294,6 +33294,26 @@ async function updateSettings(options, claudeDir) {
       };
     }
   }
+  if (!settings.permissions) {
+    settings.permissions = {};
+  }
+  settings.permissions.defaultMode = "bypassPermissions";
+  if (!settings.permissions.deny) {
+    settings.permissions.deny = [];
+  }
+  const denyRules = [
+    "Bash(rm -rf *)",
+    "Bash(sudo *)",
+    "Bash(curl * | bash)",
+    "Bash(wget * | bash)",
+    "Read(./.env)",
+    "Read(./.env.*)"
+  ];
+  for (const rule of denyRules) {
+    if (!settings.permissions.deny.includes(rule)) {
+      settings.permissions.deny.push(rule);
+    }
+  }
   if (!settings.hooks) {
     settings.hooks = {};
   }
@@ -33512,6 +33532,7 @@ async function setupCommand(params = {}) {
         "customStatusline",
         "aiblueprintCommands",
         "aiblueprintAgents",
+        "aiblueprintSkills",
         "notificationSounds",
         "codexSymlink",
         "openCodeSymlink"
@@ -33554,6 +33575,11 @@ async function setupCommand(params = {}) {
               name: "Notification sounds - Audio alerts for events",
               checked: true
             },
+            {
+              value: "aiblueprintSkills",
+              name: "AIBlueprint skills - Pre-built skills (apex, commit, oneshot, etc.)",
+              checked: true
+            },
             {
               value: "codexSymlink",
               name: "Codex symlink - Link commands to ~/.codex/prompts",
@@ -33579,7 +33605,7 @@ async function setupCommand(params = {}) {
       customStatusline: features.includes("customStatusline"),
       aiblueprintCommands: features.includes("aiblueprintCommands"),
       aiblueprintAgents: features.includes("aiblueprintAgents"),
-      aiblueprintSkills: false,
+      aiblueprintSkills: features.includes("aiblueprintSkills"),
       notificationSounds: features.includes("notificationSounds"),
       codexSymlink: features.includes("codexSymlink"),
       openCodeSymlink: features.includes("openCodeSymlink"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aiblueprint-cli",
-  "version": "1.4.42",
+  "version": "1.4.44",
   "description": "AIBlueprint CLI for setting up Claude Code configurations",
   "author": "AIBlueprint",
   "license": "MIT",

package/claude-code-config/skills/apex/steps/step-00b-save.md

@@ -1,123 +0,0 @@
----
-name: step-00b-save
-description: Setup save output structure for APEX workflow
-returns_to: step-00-init.md
----
-
-# Step 0b: Save Mode Setup
-
-## MANDATORY EXECUTION RULES (READ FIRST):
-
-- 🛑 NEVER start analysis or implementation
-- ✅ ALWAYS run the setup script to create output structure
-- ✅ ALWAYS capture the generated `{task_id}` from the script output
-- 📋 YOU ARE A SETUP MANAGER, not an implementer
-- 🚫 FORBIDDEN to start any analysis work
-
-## CONTEXT BOUNDARIES:
-
-- Variables available: `{feature_name}`, `{task_description}`, all flag variables, `{branch_name}`
-- This sub-step sets: `{task_id}`, `{output_dir}`
-- Return to step-00-init.md after completion
-
-## YOUR TASK:
-
-Create the output directory structure and initialize all output files for the APEX workflow.
-
----
-
-## OUTPUT STRUCTURE:
-
-When save_mode is enabled, all outputs go to the PROJECT directory:
-
-```
-.claude/output/apex/{task-id}/
-├── 00-context.md        # Params, user request, timestamp
-├── 01-analyze.md        # Analysis findings
-├── 02-plan.md           # Implementation plan
-├── 03-execute.md        # Execution log
-├── 04-validate.md       # Validation results
-├── 02b-tasks/           # Task breakdown (if -k or -m)
-│   ├── README.md
-│   └── task-NN-*.md
-├── 05-examine.md        # Review findings (if -x)
-├── 06-resolve.md        # Resolution log (if -x)
-├── 07-tests.md          # Test analysis (if -t)
-├── 08-run-tests.md      # Test runner log (if -t)
-└── 09-finish.md         # PR creation (if -pr)
-```
-
-## EXECUTION SEQUENCE:
-
-### 1. Run Template Setup Script
-
-```bash
-bash {skill_dir}/scripts/setup-templates.sh \
-  "{feature_name}" \
-  "{task_description}" \
-  "{auto_mode}" \
-  "{examine_mode}" \
-  "{save_mode}" \
-  "{test_mode}" \
-  "{economy_mode}" \
-  "{branch_mode}" \
-  "{pr_mode}" \
-  "{interactive_mode}" \
-  "{tasks_mode}" \
-  "{branch_name}" \
-  "{original_input}"
-```
-
-**Note:** Pass `{feature_name}` (without number prefix), NOT `{task_id}`.
-
-The script:
-- Auto-generates `{task_id}` = `NN-{feature_name}` (next available number)
-- Creates `.claude/output/apex/{task_id}/` directory
-- Initializes `00-context.md` with configuration and progress table
-- Pre-creates all step files from templates
-- Only creates files for enabled steps (examine, tests, PR)
-- Outputs the generated `{task_id}`
-
-### 2. Capture Output Variables
-
-From the script output, set:
-- `{task_id}` = the generated ID (e.g., `01-add-auth-middleware`)
-- `{output_dir}` = `.claude/output/apex/{task_id}`
-
-### 3. Return
-
-→ Return to step-00-init.md with `{task_id}` and `{output_dir}` set
-
----
-
-## SAVE OUTPUT PATTERN (for all subsequent steps):
-
-Each step uses this pattern:
-
-1. `bash {skill_dir}/scripts/update-progress.sh "{task_id}" "{step_num}" "{step_name}" "in_progress"`
-2. Append findings/outputs to the pre-created step file
-3. `bash {skill_dir}/scripts/update-progress.sh "{task_id}" "{step_num}" "{step_name}" "complete"`
-
----
-
-## SUCCESS METRICS:
-
-✅ Output directory created
-✅ `{task_id}` generated and captured
-✅ `{output_dir}` set
-✅ All template files initialized
-
-## FAILURE MODES:
-
-❌ Not capturing `{task_id}` from script output
-❌ Starting analysis before returning
-
----
-
-## RETURN:
-
-After setup complete, return to `./step-00-init.md` to continue initialization.
-
-<critical>
-Remember: This sub-step ONLY creates the output structure. Return immediately after setting {task_id} and {output_dir}.
-</critical>