@slamb2k/mad-skills 2.0.43 → 2.0.45

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mad-skills",
   "description": "AI-assisted planning, development and governance tools",
-  "version": "2.0.43",
+  "version": "2.0.45",
   "author": {
     "name": "slamb2k",
     "url": "https://github.com/slamb2k"

package/hooks/lib/state.cjs

@@ -70,4 +70,33 @@ function savePrefs(projectDir, prefs) {
   writeFileSync(prefsPath(projectDir), JSON.stringify(prefs, null, 2));
 }
 
-module.exports = { save, load, clear, isRecentlyChecked, loadPrefs, savePrefs };
+// ─── pending build marker ─────────────────────────────────────────────
+
+function pendingBuildPath(projectDir) {
+  return join(STATE_DIR, `${projectKey(projectDir)}-pending-build.json`);
+}
+
+function savePendingBuild(projectDir, specPath) {
+  ensureDir();
+  writeFileSync(pendingBuildPath(projectDir), JSON.stringify({
+    specPath,
+    projectDir,
+    timestamp: Date.now(),
+  }, null, 2));
+}
+
+function loadPendingBuild(projectDir) {
+  const path = pendingBuildPath(projectDir);
+  if (!existsSync(path)) return null;
+  try {
+    return JSON.parse(readFileSync(path, 'utf-8'));
+  } catch {
+    return null;
+  }
+}
+
+function clearPendingBuild(projectDir) {
+  try { unlinkSync(pendingBuildPath(projectDir)); } catch { /* noop */ }
+}
+
+module.exports = { save, load, clear, isRecentlyChecked, loadPrefs, savePrefs, savePendingBuild, loadPendingBuild, clearPendingBuild };

package/hooks/session-guard.cjs

@@ -80,7 +80,10 @@ function check() {
   // 3) Staleness evaluation
   checkStaleness(PROJECT_DIR, CLAUDE_MD, gitRoot, output);
 
-  // 4) Staleness summary
+  // 4) Pending build check
+  checkPendingBuild(PROJECT_DIR, output);
+
+  // 5) Staleness summary
   if (output.score >= config.staleness.threshold) {
     output.blank();
     output.add(`[SESSION GUARD] \u26A0\uFE0F  CLAUDE.md appears STALE (score: ${output.score}/${config.staleness.threshold})`);
@@ -231,6 +234,26 @@ function checkRig(projectDir, output) {
   );
 }
 
+// ─── pending build check ──────────────────────────────────────────────
+
+function checkPendingBuild(projectDir, output) {
+  const pending = state.loadPendingBuild(projectDir);
+  if (!pending) return;
+
+  const specPath = pending.specPath;
+  const specExists = existsSync(join(projectDir, specPath));
+
+  if (!specExists) {
+    // Spec file was deleted — clean up stale marker
+    state.clearPendingBuild(projectDir);
+    return;
+  }
+
+  output.blank();
+  output.add(`[SESSION GUARD] 📋 Pending spec ready for build: ${specPath}`);
+  output.add(`[SESSION GUARD] → Run: /build ${specPath}`);
+}
+
 // ─── helpers ───────────────────────────────────────────────────────────
 
 function emit(output) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@slamb2k/mad-skills",
-  "version": "2.0.43",
+  "version": "2.0.45",
   "description": "Claude Code skills collection — full lifecycle development tools",
   "type": "module",
   "repository": {

package/skills/build/SKILL.md

@@ -102,16 +102,31 @@ For each row, in order:
 4. After all checks: summarize what's available and what's degraded
 
 1. Capture **PLAN** (the user's argument) and **FLAGS**
-2. **Load project context** — invoke `/prime` to load domain-specific context
+2. **Clear pending-build marker** — if a marker was left by `/speccy`, clear it:
+   ```bash
+   PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/slamb2k}"
+   node -e "require('$PLUGIN_ROOT/hooks/lib/state.cjs').clearPendingBuild(process.cwd())"
+   ```
+3. **Load project context** — invoke `/prime` to load domain-specific context
    (CLAUDE.md, specs, memory). If /prime is unavailable, fall back to
    manually scanning CLAUDE.md and specs/ directory.
-3. Detect project type using `references/project-detection.md` to populate
+4. Detect project type using `references/project-detection.md` to populate
    **PROJECT_CONFIG** (language, test_runner, test_setup)
-3. Check for outstanding items from previous work:
+5. **Create task list** — ALWAYS create tasks upfront for all stages using
+   `TaskCreate`. This provides visible progress tracking throughout the build:
+   - Task: "Stage 1: Explore codebase"
+   - Task: "Stage 2: Clarifying questions" (if not `--skip-questions`)
+   - Task: "Stage 3: Architecture design"
+   - Task: "Stage 4: Implementation"
+   - Task: "Stage 5: Code review" (if not `--skip-review`)
+   - Task: "Stage 7: Verify"
+   - Task: "Stage 9: Ship" (if not `--no-ship`)
+   Mark each task `in_progress` when starting and `completed` when done.
+6. Check for outstanding items from previous work:
    - Query persistent tasks via `TaskList` for incomplete items
    - Search CLAUDE.md for a "Known Issues" or "Open Questions" section
    - Search memory (if available) for recent unresolved items
-4. If outstanding items found, present via AskUserQuestion:
+7. If outstanding items found, present via AskUserQuestion:
    ```
    "Found {count} outstanding items from previous work:"
    {numbered list with summary of each}
@@ -226,10 +241,13 @@ If rejected, incorporate feedback and re-run.
 
 ## Stage 4: Implementation
 
-If `--parallel-impl` and ARCH_REPORT has independent `parallel_groups`,
-launch **multiple general-purpose subagents in parallel**.
+If ARCH_REPORT identifies independent `parallel_groups`, launch **multiple
+general-purpose subagents in parallel** — one per group. Do NOT wait for
+`--parallel-impl` flag; parallel execution is the **default** when the
+architecture supports it. The flag is retained only as an explicit override.
 
-Otherwise launch **one general-purpose subagent**:
+If the architecture has no independent groups, launch **one general-purpose
+subagent**:
 
 ```
 Task(

package/skills/manifest.json

@@ -1,5 +1,5 @@
 {
-  "generated": "2026-03-24T08:38:36.091Z",
+  "generated": "2026-03-24T21:58:11.133Z",
   "count": 10,
   "skills": [
     {
@@ -16,7 +16,7 @@
       "name": "build",
       "directory": "build",
       "description": "Context-isolated feature development pipeline. Takes a detailed design/plan as argument and executes the full feature-dev lifecycle (explore, question, architect, implement, review, ship) inside subagents so the primary conversation stays compact. Use when you have a well-defined plan and want autonomous execution with minimal context window consumption.",
-      "lines": 438,
+      "lines": 456,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": false,

package/skills/speccy/SKILL.md

@@ -232,28 +232,28 @@ After the spec is created, report to the user:
 └─────────────────────────────────────────────────
 ```
 
-Then **immediately** ask the user via AskUserQuestion:
+Then write a **pending-build marker** so the next session knows about this spec:
 
-   Question: "Spec written to {spec file path}. Ready to build?"
-   Options:
-   - "Build now (Recommended)" — invoke `/build` immediately
-   - "Review first" — stop here so the user can review the spec before building
-   - "Done" — stop here, no build
+```bash
+PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/slamb2k}"
+node -e "require('$PLUGIN_ROOT/hooks/lib/state.cjs').savePendingBuild(process.cwd(), '{spec file path}')"
+```
 
-If the user selects **"Build now"**:
-1. Invoke `/build {spec file path}` directly:
-   ```
-   Skill(skill: "build", args: "{spec file path}")
-   ```
-   `/build` reads the spec file via Plan Resolution and executes the full
-   pipeline. **Do not** attempt to implement the spec yourself — always
-   delegate to `/build`.
+This marker is picked up by the session-guard hook on the next session start
+(including after `/clear`), which surfaces the build command automatically.
+
+Then display the build command:
 
-If the user selects **"Review first"** or **"Done"**, stop and display:
 ```
-⚡ To build later, run: /build {spec file path}
+⚡ To implement, run: /build {spec file path}
+   (You can /clear first — the spec is saved and the next session will remind you)
 ```
 
-**IMPORTANT:** After generating the spec, do NOT enter plan mode, do NOT
-start implementing directly, and do NOT offer to execute the plan yourself.
-The only path to implementation is through `/build`.
+The spec file persists on disk, so the user can `/clear` the conversation
+to free context before running `/build`. This is the recommended flow for
+large specs — clearing context gives `/build` maximum working room.
+
+**IMPORTANT:** After generating the spec, STOP. Do NOT enter plan mode,
+do NOT start implementing directly, do NOT invoke `/build` yourself, and
+do NOT offer to execute the plan. The spec file is the handoff artifact —
+the user controls when and how to invoke `/build`.