@juancr11/sibu 0.14.0 → 0.16.0

package/bin/admin/release.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { createInterface } from 'node:readline/promises';
-import { execFileSync } from 'node:child_process';
+import { execFileSync, spawnSync } from 'node:child_process';
 import fs from 'node:fs';
 import { fileURLToPath } from 'node:url';
 import { previewAndConfirmMaintainerRelease } from '../modules/maintainer-release-support/release-workflow/handler.js';
@@ -166,6 +166,20 @@ function createTerminalPorts() {
                 return commandFailure(error);
             }
         },
+        runInteractive(command, args) {
+            const result = spawnSync(command, args, {
+                stdio: 'inherit',
+            });
+            if (result.error) {
+                return {
+                    exitCode: 1,
+                    stderr: result.error.message,
+                };
+            }
+            return {
+                exitCode: result.status ?? 1,
+            };
+        },
     };
 }
 function printExecutionResult(result, ports) {

package/bin/modules/maintainer-release-support/release-workflow/handler.js

@@ -207,8 +207,9 @@ export async function executeConfirmedRelease(plan, ports) {
     }
     const npmPublishArgs = buildNpmPublishArgs(plan);
     const npmPublishLog = plan.hasOtp ? 'npm publish --access public --otp ******' : 'npm publish --access public';
-    printExecutionProgress(ports, `Publishing package to npm: ${npmPublishLog}...`);
-    const npmPublish = await ports.run('npm', npmPublishArgs);
+    const npmPublishMode = plan.hasOtp ? 'captured OTP publish' : 'interactive browser/2FA-capable publish';
+    printExecutionProgress(ports, `Publishing package to npm: ${npmPublishLog} (${npmPublishMode})...`);
+    const npmPublish = await runNpmPublish(ports, npmPublishArgs, plan);
     if (npmPublish.exitCode !== 0) {
         const failure = failExecution(completedSteps, 'publish-npm', 'Publishing to npm failed.', npmPublish);
         printExecutionFailure(ports, failure);
@@ -272,6 +273,12 @@ function buildNpmPublishArgs(plan) {
     }
     return args;
 }
+function runNpmPublish(ports, args, plan) {
+    if (plan.hasOtp || !ports.runInteractive) {
+        return ports.run('npm', args);
+    }
+    return ports.runInteractive('npm', args);
+}
 async function runStep(ports, completedSteps, stepName, startMessage, command, args, completedMessage) {
     printExecutionProgress(ports, startMessage);
     const result = await ports.run(command, args);

package/bin/modules/skill-selection-management/stop-managing-file/handler.js

@@ -10,7 +10,7 @@ import { renderIntro } from '../../interactive-guidance/index.js';
 import { cloneState, readStateForDoctor, writeStateFile } from '../../workflow-state-registry/index.js';
 import { getTemplateVersion, readTemplateManifest, renderTemplateForSync } from '../../template-catalog-rendering/index.js';
 import { removeUndefinedFields } from '../../../shared/object.js';
-import { getSelectedAgentsFromState, getSelectedArchitectureSkillFromState, getSelectedDatabaseSkillsFromState, getSelectedFrameworkSkillsFromState, getSelectedLanguageSkillsFromState, getSelectedWorkflowSkillsFromState, } from '../../workflow-target-planning/index.js';
+import { getSelectedAgentsFromState, getSelectedArchitectureSkillFromState, getSelectedDatabaseSkillsFromState, getSelectedFrameworkSkillsFromState, getSelectedLanguageSkillsFromState, getSelectedWorkflowSkillsFromState, getSkillTargetsForAgents, } from '../../workflow-target-planning/index.js';
 export async function handleStopManagingFile({ skillName }) {
     await renderIntro();
     intro(chalk.cyan('Updating skill management'));
@@ -136,13 +136,7 @@ function removeSelectedSkill(state, resolved) {
     }
 }
 function getSkillManagedPaths(rootPath, state, resolved) {
-    const relativePaths = new Set();
-    for (const agent of getSelectedAgentsFromState(state)) {
-        const relativePath = resolved.skill.targetRelativePathsByAgent[agent.id];
-        if (relativePath) {
-            relativePaths.add(relativePath);
-        }
-    }
+    const relativePaths = new Set(getSkillTargetsForAgents(resolved.skill, getSelectedAgentsFromState(state)).map((target) => target.targetRelativePath));
     return [...relativePaths].map((relativePath) => ({
         relativePath,
         absolutePath: path.join(rootPath, relativePath),

package/bin/modules/sync-review/sync-preview.js

@@ -3,7 +3,7 @@ import path from 'node:path';
 import { sha256 } from '../../shared/hash.js';
 import { hasReviewedTemplateVersion } from '../workflow-state-registry/index.js';
 import { renderTemplateForSync } from '../template-catalog-rendering/index.js';
-import { getSelectedAgentsFromState, getSelectedArchitectureSkillFromState, getSelectedDatabaseSkillsFromState, getSelectedFrameworkSkillsFromState, getSelectedLanguageSkillsFromState, getSelectedMcpServersFromState, getSelectedWorkflowSkillsFromState, getWorkflowSkillsImpliedByMcpServers, getWorkflowTargets, } from '../workflow-target-planning/index.js';
+import { getSelectedAgentsFromState, getSelectedArchitectureSkillFromState, getSelectedDatabaseSkillsFromState, getSelectedFrameworkSkillsFromState, getSelectedLanguageSkillsFromState, getSelectedMcpServersFromState, getSelectedWorkflowSkillsFromState, getSkillTargetsForAgents, getWorkflowSkillsImpliedByMcpServers, getWorkflowTargets, } from '../workflow-target-planning/index.js';
 const ACTIONABLE_SYNC_PREVIEW_STATUSES = new Set([
     'new-template',
     'missing',
@@ -39,7 +39,7 @@ export function getSyncPreviews({ rootPath, state, manifest }) {
     const expectedTargets = getWorkflowTargets(rootPath, getSelectedAgentsFromState(state), selectedLanguageSkills, selectedFrameworkSkills, selectedArchitectureSkill, plannedWorkflowSkills, selectedDatabaseSkills, selectedMcpServers);
     const alreadyPreviewedPaths = new Set();
     for (const skill of missingImpliedWorkflowSkills) {
-        for (const preview of getNewExpectedTargetPreviews({ rootPath, manifest, state, expectedTargets, workflowSkill: skill })) {
+        for (const preview of getNewExpectedTargetPreviews({ rootPath, manifest, state, expectedTargets, selectedAgents: getSelectedAgentsFromState(state), workflowSkill: skill })) {
             previews.push(preview);
             alreadyPreviewedPaths.add(preview.relativePath);
         }
@@ -65,8 +65,8 @@ export function getSyncPreviews({ rootPath, state, manifest }) {
     }
     return previews;
 }
-function getNewExpectedTargetPreviews({ rootPath, manifest, state, expectedTargets, workflowSkill, }) {
-    const workflowSkillTargetPaths = new Set(Object.values(workflowSkill.targetRelativePathsByAgent));
+function getNewExpectedTargetPreviews({ rootPath, manifest, state, expectedTargets, selectedAgents, workflowSkill, }) {
+    const workflowSkillTargetPaths = new Set(getSkillTargetsForAgents(workflowSkill, selectedAgents).map((target) => target.targetRelativePath));
     return expectedTargets
         .filter((target) => workflowSkillTargetPaths.has(path.relative(rootPath, target.targetPath)))
         .filter((target) => !state.managedFiles[path.relative(rootPath, target.targetPath)])

package/bin/modules/template-catalog-rendering/templates.js

@@ -45,7 +45,7 @@ export function renderMcpConfig({ agentId, baseContents, selectedMcpServers, })
     if (agentId === 'codex') {
         return renderCodexMcpConfig(baseContents ?? '', selectedMcpServers);
     }
-    return renderJsonMcpConfig(buildJsonMcpServerConfigs(agentId, selectedMcpServers));
+    return renderJsonMcpConfig(buildJsonMcpServerConfigs(agentId, selectedMcpServers), baseContents);
 }
 export function extractProjectOverview(filePath) {
     if (!fs.existsSync(filePath)) {
@@ -93,6 +93,9 @@ function getMcpConfigAgentId(templateRelativePath) {
     if (templateRelativePath === 'mcp/gemini/settings.json') {
         return 'gemini';
     }
+    if (templateRelativePath === '.gemini/settings.json') {
+        return 'gemini';
+    }
     return undefined;
 }
 function buildJsonMcpServerConfigs(agentId, selectedMcpServers) {
@@ -128,8 +131,20 @@ function buildNotionMcpServerConfig() {
         url: 'https://mcp.notion.com/mcp',
     };
 }
-function renderJsonMcpConfig(mcpServers) {
-    return `${JSON.stringify({ mcpServers }, null, 2)}\n`;
+function renderJsonMcpConfig(mcpServers, baseContents) {
+    const baseConfig = parseJsonObject(baseContents);
+    baseConfig.mcpServers = mcpServers;
+    return `${JSON.stringify(baseConfig, null, 2)}\n`;
+}
+function parseJsonObject(contents) {
+    if (!contents?.trim()) {
+        return {};
+    }
+    const parsed = JSON.parse(contents);
+    if (!parsed || typeof parsed !== 'object' || Array.isArray(parsed)) {
+        throw new Error('Expected JSON template to contain an object.');
+    }
+    return parsed;
 }
 function isTemplateManifest(value) {
     if (!value || typeof value !== 'object') {

package/bin/modules/workflow-target-planning/catalog.js

@@ -81,6 +81,23 @@ export const MANDATORY_SKILLS = [
         },
     },
 ];
+export const SESSION_START_HOOKS = [
+    {
+        agentId: 'codex',
+        templateRelativePath: '.codex/hooks.json',
+        targetRelativePath: '.codex/hooks.json',
+    },
+    {
+        agentId: 'gemini',
+        templateRelativePath: '.gemini/settings.json',
+        targetRelativePath: '.gemini/settings.json',
+    },
+    {
+        agentId: 'claude',
+        templateRelativePath: '.claude/settings.json',
+        targetRelativePath: '.claude/settings.json',
+    },
+];
 export const SELECTABLE_LANGUAGE_SKILLS = [
     {
         id: 'typescript',
@@ -232,6 +249,26 @@ export const SELECTABLE_WORKFLOW_SKILLS = [
             claude: '.agents/skills/export-to-github/SKILL.md',
             windsurf: '.agents/skills/export-to-github/SKILL.md',
         },
+        supplementalTargetsByAgent: {
+            codex: [
+                {
+                    templateRelativePath: '.codex/agents/github-exporter.toml',
+                    targetRelativePath: '.codex/agents/github-exporter.toml',
+                },
+            ],
+            gemini: [
+                {
+                    templateRelativePath: '.gemini/agents/github-exporter.md',
+                    targetRelativePath: '.gemini/agents/github-exporter.md',
+                },
+            ],
+            claude: [
+                {
+                    templateRelativePath: '.claude/agents/github-exporter.md',
+                    targetRelativePath: '.claude/agents/github-exporter.md',
+                },
+            ],
+        },
     },
     {
         id: 'export-to-notion',
@@ -245,6 +282,26 @@ export const SELECTABLE_WORKFLOW_SKILLS = [
             claude: '.agents/skills/export-to-notion/SKILL.md',
             windsurf: '.agents/skills/export-to-notion/SKILL.md',
         },
+        supplementalTargetsByAgent: {
+            codex: [
+                {
+                    templateRelativePath: '.codex/agents/notion-exporter.toml',
+                    targetRelativePath: '.codex/agents/notion-exporter.toml',
+                },
+            ],
+            gemini: [
+                {
+                    templateRelativePath: '.gemini/agents/notion-exporter.md',
+                    targetRelativePath: '.gemini/agents/notion-exporter.md',
+                },
+            ],
+            claude: [
+                {
+                    templateRelativePath: '.claude/agents/notion-exporter.md',
+                    targetRelativePath: '.claude/agents/notion-exporter.md',
+                },
+            ],
+        },
     },
 ];
 const EXPORT_WORKFLOW_SKILL_MCP_REQUIREMENTS = {

package/bin/modules/workflow-target-planning/index.js

@@ -1,2 +1,2 @@
-export { MANDATORY_SKILLS, SELECTABLE_ARCHITECTURE_SKILLS, SELECTABLE_DATABASE_SKILLS, SELECTABLE_FRAMEWORK_SKILLS, SELECTABLE_LANGUAGE_SKILLS, SELECTABLE_MCP_SERVERS, SELECTABLE_WORKFLOW_SKILLS, SUPPORTED_AGENTS, getMcpServersRequiredByWorkflowSkills, getWorkflowSkillsImpliedByMcpServers, resolveSelectableMcpServerById, resolveSelectableSkillById, } from './catalog.js';
-export { getSelectedAgentsFromState, getSelectedArchitectureSkillFromState, getSelectedDatabaseSkillsFromState, getSelectedFrameworkSkillsFromState, getSelectedLanguageSkillsFromState, getSelectedMcpServersFromState, getSelectedMcpTargetsForAgents, getSelectedSkillTargetsForAgents, getSelectedWorkflowSkillsFromState, getWorkflowTargets, renderMissingWorkflowFiles, writeSibuState, } from './workflow-targets.js';
+export { MANDATORY_SKILLS, SELECTABLE_ARCHITECTURE_SKILLS, SELECTABLE_DATABASE_SKILLS, SELECTABLE_FRAMEWORK_SKILLS, SELECTABLE_LANGUAGE_SKILLS, SELECTABLE_MCP_SERVERS, SELECTABLE_WORKFLOW_SKILLS, SESSION_START_HOOKS, SUPPORTED_AGENTS, getMcpServersRequiredByWorkflowSkills, getWorkflowSkillsImpliedByMcpServers, resolveSelectableMcpServerById, resolveSelectableSkillById, } from './catalog.js';
+export { getSelectedAgentsFromState, getSelectedArchitectureSkillFromState, getSelectedDatabaseSkillsFromState, getSelectedFrameworkSkillsFromState, getSelectedLanguageSkillsFromState, getSelectedMcpServersFromState, getSelectedMcpTargetsForAgents, getSelectedSkillTargetsForAgents, getSelectedWorkflowSkillsFromState, getSkillTargetsForAgents, getWorkflowTargets, renderMissingWorkflowFiles, writeSibuState, } from './workflow-targets.js';

package/bin/modules/workflow-target-planning/workflow-targets.js

@@ -1,7 +1,7 @@
 import fs from 'node:fs';
 import path from 'node:path';
 import { SIBU_VERSION } from '../version-advisory/index.js';
-import { MANDATORY_SKILLS, SELECTABLE_ARCHITECTURE_SKILLS, SELECTABLE_DATABASE_SKILLS, SELECTABLE_FRAMEWORK_SKILLS, SELECTABLE_LANGUAGE_SKILLS, SELECTABLE_MCP_SERVERS, SELECTABLE_WORKFLOW_SKILLS, SUPPORTED_AGENTS, } from './index.js';
+import { MANDATORY_SKILLS, SELECTABLE_ARCHITECTURE_SKILLS, SELECTABLE_DATABASE_SKILLS, SELECTABLE_FRAMEWORK_SKILLS, SELECTABLE_LANGUAGE_SKILLS, SELECTABLE_MCP_SERVERS, SELECTABLE_WORKFLOW_SKILLS, SESSION_START_HOOKS, SUPPORTED_AGENTS, } from './index.js';
 import { sha256 } from '../../shared/hash.js';
 import { removeUndefinedFields } from '../../shared/object.js';
 import { readExistingState } from '../workflow-state-registry/index.js';
@@ -36,18 +36,36 @@ export function getSelectedSkillTargetsForAgents(selectedAgents, selectedLanguag
     ];
     for (const agent of selectedAgents) {
         for (const skill of selectedSkills) {
-            const targetRelativePath = skill.targetRelativePathsByAgent[agent.id];
-            if (!targetRelativePath) {
-                continue;
+            for (const skillTarget of getSkillTargetsForAgent(skill, agent.id)) {
+                skillTargets.set(skillTarget.targetRelativePath, skillTarget);
             }
-            skillTargets.set(targetRelativePath, {
-                targetRelativePath,
-                templateRelativePath: skill.templateRelativePath,
-            });
         }
     }
     return [...skillTargets.values()];
 }
+export function getSkillTargetsForAgents(skill, selectedAgents) {
+    const skillTargets = new Map();
+    for (const agent of selectedAgents) {
+        for (const skillTarget of getSkillTargetsForAgent(skill, agent.id)) {
+            skillTargets.set(skillTarget.targetRelativePath, skillTarget);
+        }
+    }
+    return [...skillTargets.values()];
+}
+function getSkillTargetsForAgent(skill, agentId) {
+    const targets = [];
+    const targetRelativePath = skill.targetRelativePathsByAgent[agentId];
+    if (targetRelativePath) {
+        targets.push({
+            targetRelativePath,
+            templateRelativePath: skill.templateRelativePath,
+        });
+    }
+    for (const supplementalTarget of skill.supplementalTargetsByAgent?.[agentId] ?? []) {
+        targets.push(supplementalTarget);
+    }
+    return targets;
+}
 export function getSelectedMcpTargetsForAgents(selectedAgents, selectedMcpServers) {
     if (selectedMcpServers.length === 0) {
         return [];
@@ -83,6 +101,13 @@ export function getSelectedMcpTargetsForAgents(selectedAgents, selectedMcpServer
         return [];
     });
 }
+function getSessionStartHookTargetsForAgents(selectedAgents) {
+    const selectedAgentIds = new Set(selectedAgents.map((agent) => agent.id));
+    return SESSION_START_HOOKS.filter((hookTemplate) => selectedAgentIds.has(hookTemplate.agentId)).map((hookTemplate) => ({
+        targetRelativePath: hookTemplate.targetRelativePath,
+        templateRelativePath: hookTemplate.templateRelativePath,
+    }));
+}
 export function getWorkflowTargets(rootPath, selectedAgents, selectedLanguageSkills = [], selectedFrameworkSkills = [], selectedArchitectureSkill, selectedWorkflowSkills = [], selectedDatabaseSkills = [], selectedMcpServers = []) {
     const targets = [
         {
@@ -113,6 +138,13 @@ export function getWorkflowTargets(rootPath, selectedAgents, selectedLanguageSki
             requiresProjectOverview: false,
             targetKind: 'skill',
         })),
+        ...getSessionStartHookTargetsForAgents(selectedAgents).map((hookTarget) => ({
+            label: hookTarget.targetRelativePath,
+            targetPath: path.join(rootPath, hookTarget.targetRelativePath),
+            templateRelativePath: hookTarget.templateRelativePath,
+            requiresProjectOverview: false,
+            targetKind: 'agent-support',
+        })),
     ];
     for (const mcpTarget of getSelectedMcpTargetsForAgents(selectedAgents, selectedMcpServers)) {
         const targetPath = path.join(rootPath, mcpTarget.targetRelativePath);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@juancr11/sibu",
-  "version": "0.14.0",
+  "version": "0.16.0",
   "description": "CLI for setting up a local AI-augmented development workflow.",
   "repository": {
     "type": "git",

package/templates/.claude/agents/github-exporter.md

@@ -0,0 +1,18 @@
+---
+name: github-exporter
+description: Exports Sibu feature epics and user stories to GitHub issues with narrow task context and no local repository writes.
+---
+
+You are the GitHub exporter sub-agent for Sibu-managed workflows.
+
+Use only the specific export packet from the main agent: feature slug or explicit planning artifact paths, target repository resolved from the current repo, the no-local-write rule, and the expected final output format. Do not rely on or request the main agent's full conversation context.
+
+Scope:
+- Export only local Epic briefs and User Story Markdown files for the requested feature.
+- Read local Markdown files as source of truth.
+- Write only to GitHub issues and native sub-issue relationships.
+- Ask for explicit opt-in before creating or modifying GitHub issues or sub-issues.
+- Do not modify local repository files or write GitHub URLs back into Markdown by default.
+- Return concise created issue URLs or numbers, sub-issue relationship results, and any errors.
+
+If issue creation, issue ID access, native sub-issue mutation, or target repository resolution is unavailable, fail clearly and do not fall back to labels, loose links, projects, or checklists.

package/templates/.claude/agents/notion-exporter.md

@@ -0,0 +1,18 @@
+---
+name: notion-exporter
+description: Exports Sibu feature documentation to Notion with narrow task context and no local repository writes.
+---
+
+You are the Notion exporter sub-agent for Sibu-managed workflows.
+
+Use only the specific export packet from the main agent: feature slug or explicit source paths, Notion destination details, the no-local-write rule, and the expected final output format. Do not rely on or request the main agent's full conversation context.
+
+Scope:
+- Export only allowed feature documentation artifacts: feature brief, UX design, and technical design.
+- Read local Markdown files as source of truth.
+- Write only to Notion.
+- Ask for explicit opt-in before creating or modifying Notion pages.
+- Do not modify local repository files or write Notion URLs back into Markdown by default.
+- Return concise created or updated Notion URLs and any errors.
+
+If required Notion MCP capabilities, destination details, or source files are missing, fail clearly instead of inventing content or destinations.

package/templates/.claude/settings.json

@@ -0,0 +1,16 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "startup",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "sh -lc 'if latest=$(npm view @juancr11/sibu version 2>/dev/null); then echo \"Sibu latest version: $latest\"; else echo \"Sibu version check unavailable; continuing to sibu doctor.\"; fi; sibu doctor || true'",
+            "timeout": 60
+          }
+        ]
+      }
+    ]
+  }
+}

package/templates/.codex/agents/github-exporter.toml

@@ -0,0 +1,20 @@
+name = "github-exporter"
+description = "Exports Sibu feature epics and user stories to GitHub issues with narrow task context and no local repository writes."
+
+developer_instructions = """
+You are the GitHub exporter sub-agent for Sibu-managed workflows.
+
+Use only the specific export packet from the main agent: feature slug or explicit planning artifact paths, target repository resolved from the current repo, the no-local-write rule, and the expected final output format. Do not rely on or request the main agent's full conversation context.
+
+If the export packet is missing required source paths, destination details, mutation approval state, or expected output format, stop and ask the main agent for the missing packet. Do not infer missing export inputs from broader conversation history.
+
+Scope:
+- Export only local Epic briefs and User Story Markdown files for the requested feature.
+- Read local Markdown files as source of truth.
+- Write only to GitHub issues and native sub-issue relationships.
+- Ask for explicit opt-in before creating or modifying GitHub issues or sub-issues.
+- Do not modify local repository files or write GitHub URLs back into Markdown by default.
+- Return concise created issue URLs or numbers, sub-issue relationship results, and any errors.
+
+If issue creation, issue ID access, native sub-issue mutation, or target repository resolution is unavailable, fail clearly and do not fall back to labels, loose links, projects, or checklists.
+"""

package/templates/.codex/agents/notion-exporter.toml

@@ -0,0 +1,20 @@
+name = "notion-exporter"
+description = "Exports Sibu feature documentation to Notion with narrow task context and no local repository writes."
+
+developer_instructions = """
+You are the Notion exporter sub-agent for Sibu-managed workflows.
+
+Use only the specific export packet from the main agent: feature slug or explicit source paths, Notion destination details, the no-local-write rule, and the expected final output format. Do not rely on or request the main agent's full conversation context.
+
+If the export packet is missing required source paths, destination details, mutation approval state, or expected output format, stop and ask the main agent for the missing packet. Do not infer missing export inputs from broader conversation history.
+
+Scope:
+- Export only allowed feature documentation artifacts: feature brief, UX design, and technical design.
+- Read local Markdown files as source of truth.
+- Write only to Notion.
+- Ask for explicit opt-in before creating or modifying Notion pages.
+- Do not modify local repository files or write Notion URLs back into Markdown by default.
+- Return concise created or updated Notion URLs and any errors.
+
+If required Notion MCP capabilities, destination details, or source files are missing, fail clearly instead of inventing content or destinations.
+"""

package/templates/.codex/hooks.json

@@ -0,0 +1,17 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "startup",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "sh -lc 'if latest=$(npm view @juancr11/sibu version 2>/dev/null); then echo \"Sibu latest version: $latest\"; else echo \"Sibu version check unavailable; continuing to sibu doctor.\"; fi; sibu doctor || true'",
+            "statusMessage": "Running Sibu session health check",
+            "timeout": 60
+          }
+        ]
+      }
+    ]
+  }
+}

package/templates/.gemini/agents/github-exporter.md

@@ -0,0 +1,18 @@
+---
+name: github-exporter
+description: Exports Sibu feature epics and user stories to GitHub issues with narrow task context and no local repository writes.
+---
+
+You are the GitHub exporter sub-agent for Sibu-managed workflows.
+
+Use only the specific export packet from the main agent: feature slug or explicit planning artifact paths, target repository resolved from the current repo, the no-local-write rule, and the expected final output format. Do not rely on or request the main agent's full conversation context.
+
+Scope:
+- Export only local Epic briefs and User Story Markdown files for the requested feature.
+- Read local Markdown files as source of truth.
+- Write only to GitHub issues and native sub-issue relationships.
+- Ask for explicit opt-in before creating or modifying GitHub issues or sub-issues.
+- Do not modify local repository files or write GitHub URLs back into Markdown by default.
+- Return concise created issue URLs or numbers, sub-issue relationship results, and any errors.
+
+If issue creation, issue ID access, native sub-issue mutation, or target repository resolution is unavailable, fail clearly and do not fall back to labels, loose links, projects, or checklists.

package/templates/.gemini/agents/notion-exporter.md

@@ -0,0 +1,18 @@
+---
+name: notion-exporter
+description: Exports Sibu feature documentation to Notion with narrow task context and no local repository writes.
+---
+
+You are the Notion exporter sub-agent for Sibu-managed workflows.
+
+Use only the specific export packet from the main agent: feature slug or explicit source paths, Notion destination details, the no-local-write rule, and the expected final output format. Do not rely on or request the main agent's full conversation context.
+
+Scope:
+- Export only allowed feature documentation artifacts: feature brief, UX design, and technical design.
+- Read local Markdown files as source of truth.
+- Write only to Notion.
+- Ask for explicit opt-in before creating or modifying Notion pages.
+- Do not modify local repository files or write Notion URLs back into Markdown by default.
+- Return concise created or updated Notion URLs and any errors.
+
+If required Notion MCP capabilities, destination details, or source files are missing, fail clearly instead of inventing content or destinations.

package/templates/.gemini/settings.json

@@ -0,0 +1,17 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "startup",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "sh -lc 'if latest=$(npm view @juancr11/sibu version 2>/dev/null); then echo \"Sibu latest version: $latest\" >&2; else echo \"Sibu version check unavailable; continuing to sibu doctor.\" >&2; fi; sibu doctor >&2 || true; printf \"%s\\n\" \"{\\\"systemMessage\\\":\\\"Sibu session health check finished. Review hook output for details.\\\"}\"'",
+            "name": "Sibu session health check",
+            "timeout": 60000
+          }
+        ]
+      }
+    ]
+  }
+}

package/templates/AGENTS.md

@@ -58,9 +58,7 @@ This repository uses Sibu to manage AI workflow setup.
 - `sibu doctor` is the read-only health check for this workflow. It inspects whether Sibu-managed files are missing, modified, unrecorded, or generated from older templates.
 - `sibu sync` is the post-init workflow maintenance command. It reviews template updates interactively, repairs missing managed files, adopts newly added managed templates, protects local edits from automatic overwrites, and lets the user apply safe updates, mark customized files as reviewed, write side templates, stop managing a file, or skip for later.
 
-At the start of each session in this repository, run `sibu doctor` once before making changes or giving workflow guidance. Treat it as a read-only preflight check. Do not rerun it before every follow-up in the same session unless workflow-managed files changed, the user asks, or you need to verify Sibu state after applying updates.
-
-After `sibu doctor` finishes, guide the user based on the outcome:
+Use `sibu doctor` as a read-only workflow health check when you need to verify Sibu-managed file state. After `sibu doctor` finishes, guide the user based on the outcome:
 
 - Healthy workflow: mention that the Sibu check passed and proceed.
 - Missing `.sibu/state.json`: tell the user to run `sibu init` once before continuing.

package/templates/manifest.json

@@ -1,11 +1,11 @@
 {
-  "templateVersion": "103",
+  "templateVersion": "110",
   "templates": {
     "AGENTS.md": {
-      "version": "30",
+      "version": "31",
       "description": "Project-level agent instructions and Sibu maintenance guidance.",
       "changes": [
-        "Routes rough future idea capture requests to the mandatory feature-idea-capture skill."
+        "Removes the manual session-start preflight instruction now that native hook files own automatic Sibu health checks."
       ]
     },
     ".codex/config.toml": {
@@ -51,31 +51,31 @@
       ]
     },
     "skills/product-vision-writer/SKILL.md": {
-      "version": "8",
+      "version": "9",
       "description": "Mandatory product vision writer skill installed once at the shared .agents/skills workspace path.",
       "changes": [
-        "Strengthens product vision interviews to resolve material strategy questions before drafting instead of leaving uncertainty in the artifact."
+        "Makes product vision discovery mandatory before drafting, even when existing context looks complete."
       ]
     },
     "skills/deep-module-map-writer/SKILL.md": {
-      "version": "4",
+      "version": "5",
       "description": "Mandatory Deep Module Map writer skill installed once at the shared .agents/skills workspace path.",
       "changes": [
-        "Adds explicit Deep Module Map discovery guidance so agents keep interviewing one question at a time until module interfaces, hidden complexity, ownership, exclusions, scenarios, relationships, and cross-module rules are clear enough to defend."
+        "Makes Deep Module Map interviews mandatory before drafting, even when repo code or existing docs look complete."
       ]
     },
     "skills/feature-brief-writer/SKILL.md": {
-      "version": "13",
+      "version": "14",
       "description": "Mandatory feature brief writer skill installed once at the shared .agents/skills workspace path.",
       "changes": [
-        "Keeps feature brief writing focused on local Markdown artifacts and moves Notion export workflow guidance to dedicated exporter skills."
+        "Makes feature brief interviews mandatory before drafting while keeping export workflows delegated to dedicated exporter skills."
       ]
     },
     "skills/technical-design-writer/SKILL.md": {
-      "version": "19",
+      "version": "20",
       "description": "Mandatory technical design writer skill installed once at the shared .agents/skills workspace path.",
       "changes": [
-        "Keeps technical design writing focused on local Markdown artifacts and moves Notion export workflow guidance to dedicated exporter skills."
+        "Makes technical design clarification mandatory before drafting while keeping export workflows delegated to dedicated exporter skills."
       ]
     },
     "skills/typescript/SKILL.md": {
@@ -89,7 +89,7 @@
       "version": "1",
       "description": "Selectable Go skill installed when Go language support is selected.",
       "changes": [
-        "Adds an optional Go skill with concise, Effective Go–style guidance for .go files, package APIs, interfaces, errors, receivers, concurrency, and tests."
+        "Adds an optional Go skill with concise, Effective Go\u2013style guidance for .go files, package APIs, interfaces, errors, receivers, concurrency, and tests."
       ]
     },
     "skills/postgresql-expert/SKILL.md": {
@@ -163,10 +163,10 @@
       ]
     },
     "skills/ux-expert/SKILL.md": {
-      "version": "9",
+      "version": "10",
       "description": "Selectable UX expert skill for UI-changing features, responsive design, flows, states, accessibility, and binding mockups.",
       "changes": [
-        "Keeps UX design writing focused on local Markdown artifacts and moves Notion export workflow guidance to dedicated exporter skills."
+        "Makes UX clarification mandatory before drafting while keeping export workflows delegated to dedicated exporter skills."
       ]
     },
     "skills/architecture/layered-architecture/SKILL.md": {
@@ -177,17 +177,80 @@
       ]
     },
     "skills/export-to-github/SKILL.md": {
-      "version": "1",
+      "version": "4",
       "description": "Selectable GitHub export skill for publishing a named feature's Epics and User Stories to GitHub issues and native sub-issues.",
       "changes": [
-        "Adds a dedicated GitHub exporter skill paired with GitHub MCP selection."
+        "Requires GitHub exports to run as non-blocking background sub-agent jobs and prevents the main agent from waiting or polling for completion."
       ]
     },
     "skills/export-to-notion/SKILL.md": {
-      "version": "1",
+      "version": "4",
       "description": "Selectable Notion export skill for publishing a named feature's core documentation files to Notion.",
       "changes": [
-        "Adds a dedicated Notion exporter skill paired with Notion MCP selection."
+        "Requires Notion exports to run as non-blocking background sub-agent jobs and prevents the main agent from waiting or polling for completion."
+      ]
+    },
+    ".codex/agents/github-exporter.toml": {
+      "version": "3",
+      "description": "Codex GitHub exporter sub-agent for Sibu feature Epic and User Story exports.",
+      "changes": [
+        "Requires the Codex github-exporter sub-agent to stop and request missing export packet details instead of inferring from broad conversation context."
+      ]
+    },
+    ".codex/agents/notion-exporter.toml": {
+      "version": "3",
+      "description": "Codex Notion exporter sub-agent for Sibu feature documentation exports.",
+      "changes": [
+        "Requires the Codex notion-exporter sub-agent to stop and request missing export packet details instead of inferring from broad conversation context."
+      ]
+    },
+    ".claude/agents/github-exporter.md": {
+      "version": "1",
+      "description": "Claude GitHub exporter sub-agent for Sibu feature Epic and User Story exports.",
+      "changes": [
+        "Adds a Claude github-exporter sub-agent with clean-context and no-local-write export guidance."
+      ]
+    },
+    ".claude/agents/notion-exporter.md": {
+      "version": "1",
+      "description": "Claude Notion exporter sub-agent for Sibu feature documentation exports.",
+      "changes": [
+        "Adds a Claude notion-exporter sub-agent with clean-context and no-local-write export guidance."
+      ]
+    },
+    ".gemini/agents/github-exporter.md": {
+      "version": "1",
+      "description": "Gemini GitHub exporter sub-agent for Sibu feature Epic and User Story exports.",
+      "changes": [
+        "Adds a Gemini github-exporter sub-agent with clean-context and no-local-write export guidance."
+      ]
+    },
+    ".gemini/agents/notion-exporter.md": {
+      "version": "1",
+      "description": "Gemini Notion exporter sub-agent for Sibu feature documentation exports.",
+      "changes": [
+        "Adds a Gemini notion-exporter sub-agent with clean-context and no-local-write export guidance."
+      ]
+    },
+    ".codex/hooks.json": {
+      "version": "1",
+      "description": "Codex SessionStart hook configuration for running Sibu session health checks.",
+      "changes": [
+        "Adds a managed Codex SessionStart hook that checks the latest Sibu version and runs sibu doctor automatically."
+      ]
+    },
+    ".claude/settings.json": {
+      "version": "1",
+      "description": "Claude Code SessionStart hook configuration for running Sibu session health checks.",
+      "changes": [
+        "Adds a managed Claude SessionStart hook that checks the latest Sibu version and runs sibu doctor automatically."
+      ]
+    },
+    ".gemini/settings.json": {
+      "version": "1",
+      "description": "Gemini CLI SessionStart hook configuration for running Sibu session health checks.",
+      "changes": [
+        "Adds a managed Gemini SessionStart hook that checks the latest Sibu version and runs sibu doctor automatically."
       ]
     }
   }

package/templates/skills/deep-module-map-writer/SKILL.md

@@ -35,7 +35,7 @@ This skill owns the Deep Module Map only. It does not own feature briefs, techni
 
 - Do not create feature briefs, technical designs, UX specs, Epics, User Stories, implementation plans, or production code.
 - Do not choose a specific internal architecture, service split, database model, framework, or team ownership structure.
-- Do not ask for or require a final confirmation summary before writing once enough Deep Module Map information is available.
+- Do not skip the interview or the final “I am clear; are you good?” check-in before writing. Once the user confirms there is nothing else to cover, write without requiring a recap, artifact approval, or separate summary confirmation.
 - Do not invent Deep Modules without grounding them in the product vision, current system behavior, and user interview.
 - Do not treat a command, screen, helper, folder, data object, or technical layer as a Deep Module merely because it exists.
 - Do not leave material module-boundary questions unresolved in the final map; keep interviewing until the user answers, confirms an assumption, or explicitly excludes the boundary.
@@ -125,6 +125,8 @@ This file is user-owned product and implementation-boundary content created or u
 
 Be deliberately interrogative before writing.
 
+This interview is mandatory and non-skippable. Even when the repository has substantial code, existing docs, an existing map, or extensive initial context, ask at least one explicit user-facing discovery question before drafting or writing the Deep Module Map. Treat code, repository artifacts, prior conversation, and initial context as useful but provisional: they can shape better questions, but they must not replace the interview or become the full source of truth for module boundaries, interfaces, hidden complexity, or ownership. Keep asking focused follow-up questions until the module decisions are clear enough to defend. Before drafting, always perform one final check-in in the spirit of: “I am clear on my end. Are you good, or is there anything else you want to cover before I proceed?” If the user adds context, incorporate or clarify it before writing.
+
 - Ask one focused question at a time.
 - Ask as many one-at-a-time questions as needed to understand the app well enough to defend the map; do not optimize for a short interview.
 - Walk down each module-boundary decision branch one by one, resolving dependencies between candidate modules before drafting.

package/templates/skills/export-to-github/SKILL.md

@@ -7,6 +7,32 @@ description: Export a named feature's Epics and User Stories from local Markdown
 
 Use this skill when the user asks to export a feature's Epics and User Stories to GitHub.
 
+## Non-blocking delegation requirement
+
+Before reading planning artifacts or calling GitHub mutation tools, check whether the configured `github-exporter` sub-agent is available for the current AI target.
+
+If available, you must delegate the export to `github-exporter`. Do not perform the export inline and do not call GitHub issue or sub-issue mutation tools from the main agent.
+
+The delegation is fire-and-notify:
+
+- Start the `github-exporter` sub-agent in the background.
+- Do not call `wait_agent`, poll for completion, spawn a status-checking agent, or otherwise block the main thread.
+- Immediately return control to the user after spawning the exporter.
+- Tell the user the export is running in the background and that completion will arrive via sub-agent notification.
+- Only inspect the final result if the user explicitly asks for status/results later, or after a sub-agent completion notification is received.
+
+Pass only a clean, narrow export packet:
+
+- feature slug or explicit planning artifact paths
+- target repository resolved from the current local repo's GitHub `origin` remote
+- the no-local-write rule
+- whether user opt-in for GitHub mutation has already been granted
+- expected final output format: created issue URLs or numbers, sub-issue relationship results, and errors
+
+Do not fork or pass the main agent's full conversation context. The exporter does not need implementation, planning, or unrelated discussion context.
+
+Inline export is allowed only when sub-agent execution is unavailable, the configured `github-exporter` is not installed, or the user explicitly asks for inline fallback after the background exporter is unavailable or failed. Before any inline mutation, clearly tell the user why delegation cannot be used.
+
 ## Required input
 
 - A feature name or feature slug.
@@ -26,7 +52,16 @@ If the feature name is ambiguous, inspect `docs/features/` and ask one focused c
    - one issue per Epic, with no labels
    - one issue per User Story, with no labels
    - each User Story issue attached as a native sub-issue of its parent Epic issue
-7. Report created issue numbers or URLs.
+7. After spawning the background exporter, immediately report that the export is running in the background. Do not wait for created issue numbers or URLs in the same turn.
+
+## Delegation self-check
+
+Before finalizing, verify:
+
+- Did I use `github-exporter` when it was available?
+- Did I avoid `wait_agent`, status polling, and duplicate status-checking agents?
+- If not, did I explicitly report why before any inline GitHub mutation?
+- Did I avoid local file writes and preserve native sub-issue requirements?
 
 ## Export rules
 

package/templates/skills/export-to-notion/SKILL.md

@@ -7,6 +7,32 @@ description: Export a named feature's local feature brief, UX design, and techni
 
 Use this skill when the user asks to export a feature's core documentation to Notion.
 
+## Non-blocking delegation requirement
+
+Before reading source docs or calling Notion mutation tools, check whether the configured `notion-exporter` sub-agent is available for the current AI target.
+
+If available, you must delegate the export to `notion-exporter`. Do not perform the export inline and do not call Notion mutation tools from the main agent.
+
+The delegation is fire-and-notify:
+
+- Start the `notion-exporter` sub-agent in the background.
+- Do not call `wait_agent`, poll for completion, spawn a status-checking agent, or otherwise block the main thread.
+- Immediately return control to the user after spawning the exporter.
+- Tell the user the export is running in the background and that completion will arrive via sub-agent notification.
+- Only inspect the final result if the user explicitly asks for status/results later, or after a sub-agent completion notification is received.
+
+Pass only a clean, narrow export packet:
+
+- feature slug or explicit source paths
+- Notion destination details
+- the no-local-write rule
+- whether user opt-in for Notion mutation has already been granted
+- expected final output format: created or updated Notion URLs and errors
+
+Do not fork or pass the main agent's full conversation context. The exporter does not need implementation, planning, or unrelated discussion context.
+
+Inline export is allowed only when sub-agent execution is unavailable, the configured `notion-exporter` is not installed, or the user explicitly asks for inline fallback after the background exporter is unavailable or failed. Before any inline mutation, clearly tell the user why delegation cannot be used.
+
 ## Required input
 
 - A feature name or feature slug.
@@ -49,7 +75,16 @@ Use this organization under the configured Notion docs parent page:
 4. Ask one explicit opt-in question before creating or modifying Notion pages.
 5. Create or reuse the repo, Features, and feature organization pages under the configured parent.
 6. Export each existing allowed artifact to its matching Notion page.
-7. Report export success or failure per artifact.
+7. After spawning the background exporter, immediately report that the export is running in the background. Do not wait for final URLs in the same turn.
+
+## Delegation self-check
+
+Before finalizing, verify:
+
+- Did I use `notion-exporter` when it was available?
+- Did I avoid `wait_agent`, status polling, and duplicate status-checking agents?
+- If not, did I explicitly report why before any inline Notion mutation?
+- Did I avoid local file writes and keep local Markdown canonical?
 
 ## Export rules
 

package/templates/skills/feature-brief-writer/SKILL.md

@@ -36,7 +36,7 @@ This skill owns the product/business shape of a feature. It does not own UI inte
 
 - Do not create or update Deep Module Maps, technical designs, UX specs, Epics, User Stories, implementation plans, or production code.
 - Do not invent Deep Modules or use modules that are absent from `docs/deep-module-map.md`.
-- Do not require a final confirmation summary before writing once enough feature brief context is available.
+- Do not skip the interview or the final “I am clear; are you good?” check-in before writing. Once the user confirms there is nothing else to cover, write without requiring a recap, artifact approval, or separate summary confirmation.
 - Do not duplicate or rewrite the product vision; apply only the relevant implications to the feature.
 - Do not leave material product, scope, success, constraint, or Deep Module fit questions unresolved in the final brief; keep interviewing until the user answers, confirms an assumption, or explicitly excludes the topic.
 
@@ -110,6 +110,8 @@ If the user asks for a feature brief from an idea in `docs/feature-ideas.md`, re
 
 Be deliberately interrogative before drafting. The feature brief should reflect the user's intent, not the assistant's assumptions.
 
+This interview is mandatory and non-skippable. Even when the user provides extensive initial context, existing docs, repo code, or a raw idea file, ask at least one explicit user-facing discovery question before drafting or writing the feature brief. Treat repository artifacts, prior conversation, existing product docs, and initial context as useful but provisional: they can shape better questions, but they must not replace the interview or become the full source of truth for feature intent, scope, success, constraints, or user value. Keep asking focused follow-up questions until the feature decisions are clear enough to defend. Before drafting, always perform one final check-in in the spirit of: “I am clear on my end. Are you good, or is there anything else you want to cover before I proceed?” If the user adds context, incorporate or clarify it before writing.
+
 - Ask one focused question at a time.
 - Keep asking until you have complete practical understanding and explicit user alignment; do not optimize for a short interview.
 - Walk down each feature decision branch one by one, resolving dependencies between product, scope, success, constraint, and module-fit decisions before drafting.

package/templates/skills/product-vision-writer/SKILL.md

@@ -33,14 +33,16 @@ Default output path: `docs/product-vision.md`.
 ### What this skill must not do
 
 - Do not create Deep Module Maps, feature briefs, technical designs, UX specs, Epics, User Stories, implementation plans, or production code.
-- Do not require a final confirmation summary before writing once enough product vision context is available.
+- Do not skip the interview or the final “I am clear; are you good?” check-in before writing. Once the user confirms there is nothing else to cover, write without requiring a recap, artifact approval, or separate summary confirmation.
 - Do not leave material strategy questions unresolved in the final document; keep interviewing until the user answers, confirms an assumption, or explicitly excludes the topic.
 
 ## Workflow
 
 ### 1. Start with discovery, not drafting
 
-Interview before writing unless the user already provided complete source material. Be deliberately interrogative: ask as many focused questions as needed to extract all material product vision decisions before drafting.
+Interview before writing. Be deliberately interrogative: ask as many focused questions as needed to extract all material product vision decisions before drafting.
+
+This interview is mandatory and non-skippable. Even when the user provides extensive initial context, existing documents, or a mature codebase, ask at least one explicit user-facing discovery question before drafting or writing the product vision. Treat repository artifacts, prior conversation, and initial context as useful but provisional: they can shape better questions, but they must not replace the interview or become the full source of truth for the user's product intent. Keep asking focused follow-up questions until the material product vision decisions are clear enough to defend. Before drafting, always perform one final check-in in the spirit of: “I am clear on my end. Are you good, or is there anything else you want to cover before I proceed?” If the user adds context, incorporate or clarify it before writing.
 
 Ask one question at a time. Walk down the product decision tree branch by branch, resolving dependencies between decisions before moving on. When useful, include a recommended answer or concise assumption so the user can confirm, correct, or reject it quickly. If a question can be answered from existing repository artifacts, inspect those artifacts instead of asking.
 

package/templates/skills/technical-design-writer/SKILL.md

@@ -36,7 +36,7 @@ Write the smallest useful technical design doc for an approved feature: enough f
 - Do not invent new Deep Modules or move work into unselected modules.
 - Do not redesign binding UX mockups.
 - Do not duplicate architecture, language, framework, or clean-code skill guidance.
-- Do not require a final confirmation summary before writing once enough technical design context is available.
+- Do not skip the interview or the final “I am clear; are you good?” check-in before writing. Once the user confirms there is nothing else to cover, write without requiring a recap, artifact approval, or separate summary confirmation.
 
 ## Grounding
 
@@ -66,6 +66,8 @@ If the feature has UI impact, require `docs/features/<feature-slug>/ux.md`. If i
 
 Be deliberately interrogative before drafting. The technical design should reflect resolved implementation direction, not risky assistant assumptions.
 
+This interview is mandatory and non-skippable. Even when the approved artifacts, repo files, codebase, or prior conversation seem complete, ask at least one explicit user-facing technical clarification question before drafting or writing the technical design. Treat repository artifacts, source docs, prior conversation, and initial context as useful but provisional for current implementation intent: they can shape better questions, but they must not replace the interview or become the full source of truth for implementation direction, boundaries, risks, or validation choices. Keep asking focused follow-up questions until the technical decisions are clear enough to defend. Before drafting, always perform one final check-in in the spirit of: “I am clear on my end. Are you good, or is there anything else you want to cover before I proceed?” If the user adds context, incorporate or clarify it before writing.
+
 - Ask one focused question at a time when repository artifacts and source docs do not resolve a material technical ambiguity.
 - Ask as many questions as required to reach complete practical understanding; do not optimize for a short interview.
 - If a question can be answered by reading repository artifacts, inspect those artifacts instead of asking.

package/templates/skills/ux-expert/SKILL.md

@@ -33,7 +33,7 @@ Act as a senior UX/UI designer. Turn an approved product artifact into usable, e
 - Do not create or update product visions, Deep Module Maps, feature briefs, technical designs, Epics, User Stories, implementation plans, or production code.
 - Do not make architecture, framework, API, data model, or file-path decisions.
 - Do not treat UX work as optional for UI-changing features; concrete mockups are required.
-- Do not require a final confirmation summary before writing once enough UX context is available.
+- Do not skip the interview or the final “I am clear; are you good?” check-in before writing. Once the user confirms there is nothing else to cover, write without requiring a recap, artifact approval, or separate summary confirmation.
 
 ## Required grounding
 
@@ -45,6 +45,8 @@ Require a product artifact such as `docs/features/<feature-slug>/feature_brief.m
 
 Be deliberately interrogative before drafting. The UX spec should reflect resolved experience direction, not assistant-invented assumptions.
 
+This interview is mandatory and non-skippable. Even when product artifacts, existing UI, repo files, or prior conversation seem complete, ask at least one explicit user-facing UX clarification question before drafting or writing the UX spec. Treat artifacts, mockups, repo context, prior conversation, and initial context as useful but provisional for current experience intent: they can shape better questions, but they must not replace the interview or become the full source of truth for user flow, hierarchy, visual direction, states, or accessibility decisions. Keep asking focused follow-up questions until the UX decisions are clear enough to defend. Before drafting, always perform one final check-in in the spirit of: “I am clear on my end. Are you good, or is there anything else you want to cover before I proceed?” If the user adds context, incorporate or clarify it before writing.
+
 - Ask one focused question at a time when product artifacts do not resolve a material UX ambiguity.
 - Ask as many questions as required to reach complete practical understanding; do not optimize for a short interview.
 - If a question can be answered by reading repository artifacts, inspect those artifacts instead of asking.