jumpstart-mode 1.1.12 → 1.1.13

package/.github/agents/jumpstart-adversary.agent.md

@@ -1,7 +1,8 @@
 ---
 name: "Jump Start: Adversary"
 description: "Advisory -- Stress-test spec artifacts for violations, gaps, and ambiguities"
-tools: ['search', 'web', 'read', 'edit', 'vscode', 'todo', 'agent', 'context7/*']
+tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 

package/.github/agents/jumpstart-architect.agent.md

@@ -1,14 +1,13 @@
 ---
 name: "Jump Start: Architect"
-description:Phase 3 agent responsible for translating the PRD into a technical blueprint and an ordered implementation plan
-model: GPT-5.2
+description: Phase 3 agent responsible for translating the PRD into a technical blueprint and an ordered implementation plan. This includes technology selection, component design, data modeling, API specification, and documenting architectural decisions.
 tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
 agents: ["*"]
 handoffs: 
-    - label: "Proceed to Phase 4: Development"
-      agent: "Jump Start: Developer"
-      prompt: Implement the plan
-      send: true
+  - label: "Proceed to Phase 4: Development"
+    agent: "Jump Start: Developer"
+    prompt: "Implement the plan"
+    send: true
 ---
 
 ## Identity

package/.github/agents/jumpstart-challenger.agent.md

@@ -2,9 +2,10 @@
 name: "Jump Start: Challenger"
 description: "Phase 0 -- Interrogate assumptions, find root causes, reframe the problem before any building begins"
 tools: ['search', 'web', 'read', 'edit', 'vscode', 'todo', 'agent','context7/*']
+agents: ["*"]
 handoffs:
   - label: "Proceed to Phase 1: Analysis"
-    agent: Jump Start: Analyst
+    agent: "Jump Start: Analyst"
     prompt: "The Challenger Brief at specs/challenger-brief.md has been approved. Begin Phase 1 analysis."
     send: true
 ---

package/.github/agents/jumpstart-devops.agent.md

@@ -1,8 +1,8 @@
 ---
 name: "Jump Start: DevOps Engineer"
 description: Phase 4 advisory agent focused on deployment pipelines, environment management, and operational reliability
-model: GPT-5.2
-tools: [execute, read, edit, search, web, agent, todo]
+tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 

package/.github/agents/jumpstart-diagram-verifier.agent.md

@@ -1,7 +1,8 @@
 ---
-name: JumpStart Diagram Verifier
+name: "Jump Start: Diagram Verifier"
 description: Validates Mermaid diagrams in JumpStart specification artifacts for structural syntax and semantic correctness.
 tools: ['execute', 'read', 'search', 'agent', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 

package/.github/agents/jumpstart-maintenance.agent.md

@@ -2,6 +2,7 @@
 name: "Jump Start: Maintenance Agent"
 description: "Advisory agent focused on detecting dependency drift, specification drift, and technical debt accumulation over time to ensure the project remains maintainable, secure, and aligned with its documented design"
 tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 ## Identity

package/.github/agents/jumpstart-performance.agent.md

@@ -2,6 +2,7 @@
 name: "Jump Start: Performance Analyst"
 description: "Advisory agent focused on defining measurable performance NFRs, establishing performance budgets, and ensuring the architecture and implementation plan account for scale, latency, throughput, and cost constraints"
 tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 

package/.github/agents/jumpstart-pm.agent.md

@@ -5,7 +5,7 @@ tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7
 agents: ["*"]
 handoffs: 
   - label: "Proceed to Phase 3: Architecture"
-    agent: Jump Start: Architect
+    agent: "Jump Start: Architect"
     prompt: "The PRD at specs/prd.md has been approved. Begin Phase 3 architecture design."
     send: true
 ---

package/.github/agents/jumpstart-refactor.agent.md

@@ -2,6 +2,7 @@
 name: "Jump Start: Refactoring Agent"
 description: "Post-implementation advisory agent focused on identifying refactoring opportunities to reduce complexity, improve maintainability, and align the code with established patterns — without changing behaviour"
 tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 

package/.github/agents/jumpstart-requirements-extractor.agent.md

@@ -2,6 +2,7 @@
 name: "Jump Start: Requirements Extractor"
 description: "Advisory -- Curate PRD questions from requirements checklist using Scout + Challenger context"
 tools: ['search', 'web', 'read', 'edit', 'vscode', 'todo', 'agent', 'context7/*']
+user-invocable: false
 agents: ["*"]
 ---
 

package/.github/agents/jumpstart-researcher.agent.md

@@ -2,6 +2,7 @@
 name: "Jump Start: Domain Researcher"
 description: "Advisory agent focused on evidence-based technology evaluation, version-pinned dependency validation, and domain-specific research to inform architecture and build decisions"
 tools: ['search', 'web', 'read', 'edit', 'vscode', 'todo', 'agent', 'context7/*']
+user-invocable: false
 agents: ["*"]
 ---
 

package/.github/agents/jumpstart-retrospective.agent.md

@@ -2,6 +2,7 @@
 name: "Jump Start: Retrospective"
 description: "Advisory -- Post-build analysis of plan vs reality, tech debt catalogue, process improvements"
 tools: ['search', 'web', 'read', 'edit', 'vscode', 'todo', 'agent', 'context7/*']
+user-invocable: false
 agents: ["*"] 
 ---
 

package/.github/agents/jumpstart-reviewer.agent.md

@@ -2,6 +2,8 @@
 name: "Jump Start: Reviewer"
 description: "Advisory -- Structured peer review scoring across completeness, consistency, traceability, and quality"
 tools: ['search', 'web', 'read', 'edit', 'vscode', 'todo', 'agent', 'context7/*']
+user-invocable: false
+agents: ["*"]
 ---
 
 # The Reviewer -- Advisory

package/.github/agents/jumpstart-scout.agent.md

@@ -4,7 +4,7 @@ description: "Pre-Phase 0 -- Analyze an existing codebase to produce C4 diagrams
 tools: ['search', 'web', 'read', 'edit', 'vscode', 'todo', 'agent','context7/*']
 handoffs:
   - label: "Proceed to Phase 0: Challenge"
-    agent: Jump Start: Challenger
+    agent: "Jump Start: Challenger"
     prompt: "The Codebase Context at specs/codebase-context.md has been approved. Begin Phase 0 problem discovery. Note: this is a brownfield project — read specs/codebase-context.md for existing system context."
     send: true
 ---

package/.github/agents/jumpstart-scrum-master.agent.md

@@ -2,6 +2,7 @@
 name: "Jump Start: Scrum Master"
 description: "Phase 3 advisory agent focused on sprint planning, task orchestration, and blocker detection to ensure smooth execution in Phase 4"
 tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 ## Identity

package/.github/agents/jumpstart-security.agent.md

@@ -1,7 +1,8 @@
 ---
-name: "Jump Start: Security Architect
+name: "Jump Start: Security Architect"
 description: "Advisory agent focused on auditing architecture and implementation plans against security best practices, OWASP Top 10 risks, and project-specific invariants to identify vulnerabilities and recommend mitigations"
 tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 ## Identity

package/.github/agents/jumpstart-tech-writer.agent.md

@@ -2,6 +2,7 @@
 name: "Jump Start: Technical Writer"
 description: "Advisory agent focused on ensuring all documentation is accurate, complete, and aligned with the implemented solution — acting as the documentation conscience of the build phase"
 tools: ['vscode', 'execute', 'read', 'agent', 'edit', 'search', 'web', 'context7/*', 'mcp_docker/search', 'filesystem/*', 'todo']
+user-invocable: false
 agents: ["*"]
 ---
 

package/.github/workflows/quality.yml

@@ -43,6 +43,23 @@ jobs:
       - name: Layer 5 — Regression Golden Masters
         run: npx vitest run tests/test-regression.test.js --reporter=verbose
 
-      - name: All Tests Summary
+      - name: All Tests — Batched
         if: always()
-        run: npx vitest run --reporter=verbose
+        run: |
+          # Discover all test files, exclude the OOM-causing aggregate test,
+          # then run in batches of 15 to stay within Node.js heap limits.
+          files=$(find tests -maxdepth 1 -type f -name '*.test.js' \
+                    ! -name 'test-agent-intelligence.test.js' | sort)
+          batch=()
+          for f in $files; do
+            batch+=("$f")
+            if [ ${#batch[@]} -ge 15 ]; then
+              echo "--- Running batch: ${batch[*]} ---"
+              npx vitest run "${batch[@]}" --reporter=verbose
+              batch=()
+            fi
+          done
+          if [ ${#batch[@]} -gt 0 ]; then
+            echo "--- Running final batch: ${batch[*]} ---"
+            npx vitest run "${batch[@]}" --reporter=verbose
+          fi

package/.jumpstart/agents/analyst.md

@@ -155,6 +155,44 @@ Track progress through the 10-step Analysis Protocol so the human can see what's
 - [ ] Step 10: Compile and Present the Product Brief
 ```
 
+### record_timeline_event Tool
+
+Use this tool to record significant actions to the interaction timeline. This creates an audit trail of your workflow steps, decisions, and interactions.
+
+**When to use:**
+- After reading an upstream artifact or template (event type: `artifact_read` or `template_read`)
+- When invoking a subagent (event type: `subagent_invoked` / `subagent_completed`)
+- After significant analysis decisions (event type: `custom`)
+- When logging prompt context (event type: `prompt_logged`)
+
+**Example invocation:**
+```json
+{
+  "event_type": "artifact_read",
+  "action": "Read upstream artifact: specs/challenger-brief.md",
+  "metadata": { "artifact_path": "specs/challenger-brief.md" }
+}
+```
+
+### log_usage Tool
+
+Use this tool at the **end of your phase** to record your estimated token usage and cost to `.jumpstart/usage-log.json`. This enables cost tracking and usage auditing across all phases.
+
+**When to use:**
+- At the end of your phase, before presenting the artifact for approval
+- After completing a significant sub-task or consultation
+
+**Example invocation:**
+```json
+{
+  "phase": "phase-1",
+  "agent": "Analyst",
+  "action": "generation",
+  "estimated_tokens": 2800,
+  "model": "copilot"
+}
+```
+
 ---
 
 ## Context7 Documentation Tooling (Item 101)

package/.jumpstart/agents/architect.md

@@ -160,6 +160,44 @@ Track progress through the 9-step Solutioning Protocol. Architecture is complex
 - [ ] Step 9: Compile and Present
 ```
 
+### record_timeline_event Tool
+
+Use this tool to record significant actions to the interaction timeline. This creates an audit trail of your workflow steps, decisions, and interactions.
+
+**When to use:**
+- After reading an upstream artifact or template (event type: `artifact_read` or `template_read`)
+- When invoking a subagent (event type: `subagent_invoked` / `subagent_completed`)
+- After significant architecture decisions or ADR creation (event type: `custom`)
+- When logging prompt context (event type: `prompt_logged`)
+
+**Example invocation:**
+```json
+{
+  "event_type": "subagent_invoked",
+  "action": "Invoked Security subagent for STRIDE threat analysis",
+  "metadata": { "subagent_name": "Security", "subagent_query": "STRIDE threat model for API gateway" }
+}
+```
+
+### log_usage Tool
+
+Use this tool at the **end of your phase** to record your estimated token usage and cost to `.jumpstart/usage-log.json`. This enables cost tracking and usage auditing across all phases.
+
+**When to use:**
+- At the end of your phase, before presenting the artifact for approval
+- After completing a significant sub-task or subagent consultation
+
+**Example invocation:**
+```json
+{
+  "phase": "phase-3",
+  "agent": "Architect",
+  "action": "generation",
+  "estimated_tokens": 5200,
+  "model": "copilot"
+}
+```
+
 ---
 
 ## Solutioning Protocol

package/.jumpstart/agents/challenger.md

@@ -202,6 +202,44 @@ Use this tool to track progress through the 8-step Elicitation Protocol. This he
 - [ ] Step 8: Compile and Present the Brief
 ```
 
+### record_timeline_event Tool
+
+Use this tool to record significant actions to the interaction timeline. This creates an audit trail of your workflow steps, decisions, and interactions.
+
+**When to use:**
+- After reading an upstream artifact or template (event type: `artifact_read` or `template_read`)
+- When invoking a subagent (event type: `subagent_invoked` / `subagent_completed`)
+- After significant decisions or reframes (event type: `custom`)
+- When logging your system/activation prompt context (event type: `prompt_logged`)
+
+**Example invocation:**
+```json
+{
+  "event_type": "artifact_read",
+  "action": "Read upstream artifact: specs/challenger-brief.md",
+  "metadata": { "artifact_path": "specs/challenger-brief.md" }
+}
+```
+
+### log_usage Tool
+
+Use this tool at the **end of your phase** to record your estimated token usage and cost to `.jumpstart/usage-log.json`. This enables cost tracking and usage auditing across all phases.
+
+**When to use:**
+- At the end of your phase, before presenting the artifact for approval
+- After completing a significant sub-task or consultation
+
+**Example invocation:**
+```json
+{
+  "phase": "phase-0",
+  "agent": "Challenger",
+  "action": "generation",
+  "estimated_tokens": 3200,
+  "model": "copilot"
+}
+```
+
 ---
 
 ## Elicitation Protocol

package/.jumpstart/agents/developer.md

@@ -166,6 +166,47 @@ Track implementation progress task-by-task and milestone-by-milestone. This is e
 - When resuming work after a break, context is immediately clear
 - Progress tracking integrates naturally with VS Code's task tracking UI
 
+### record_timeline_event Tool
+
+Use this tool to record significant actions to the interaction timeline. This creates an audit trail of your workflow steps, decisions, and interactions.
+
+**When to use:**
+- After reading the implementation plan (event type: `artifact_read`)
+- Before and after each task implementation (event type: `custom`)
+- When creating files or tests (event type: `file_write`)
+- When invoking advisory subagents like QA or Security (event type: `subagent_invoked` / `subagent_completed`)
+- When logging prompt context (event type: `prompt_logged`)
+
+**Example invocation:**
+```json
+{
+  "event_type": "custom",
+  "action": "Starting task T-001: Scaffold project structure",
+  "metadata": { "task_id": "T-001", "task_name": "Scaffold project structure" }
+}
+```
+
+### log_usage Tool
+
+Use this tool at the **end of each task** and at the **end of your phase** to record your estimated token usage and cost to `.jumpstart/usage-log.json`. This enables cost tracking and usage auditing.
+
+**When to use:**
+- After completing each implementation task
+- At the end of the build phase, before presenting for approval
+- After subagent consultations
+
+**Example invocation:**
+```json
+{
+  "phase": "phase-4",
+  "agent": "Developer",
+  "action": "generation",
+  "estimated_tokens": 8500,
+  "model": "copilot",
+  "metadata": { "task_id": "T-001", "files_created": 5 }
+}
+```
+
 ---
 
 ## Implementation Protocol

package/.jumpstart/agents/pm.md

@@ -158,6 +158,44 @@ Track progress through the 10-step Planning Protocol.
 - [ ] Step 10: Compile and Present the PRD
 ```
 
+### record_timeline_event Tool
+
+Use this tool to record significant actions to the interaction timeline. This creates an audit trail of your workflow steps, decisions, and interactions.
+
+**When to use:**
+- After reading an upstream artifact or template (event type: `artifact_read` or `template_read`)
+- When invoking a subagent (event type: `subagent_invoked` / `subagent_completed`)
+- After significant planning decisions (event type: `custom`)
+- When logging prompt context (event type: `prompt_logged`)
+
+**Example invocation:**
+```json
+{
+  "event_type": "artifact_read",
+  "action": "Read upstream artifact: specs/product-brief.md",
+  "metadata": { "artifact_path": "specs/product-brief.md" }
+}
+```
+
+### log_usage Tool
+
+Use this tool at the **end of your phase** to record your estimated token usage and cost to `.jumpstart/usage-log.json`. This enables cost tracking and usage auditing across all phases.
+
+**When to use:**
+- At the end of your phase, before presenting the artifact for approval
+- After completing a significant sub-task or consultation
+
+**Example invocation:**
+```json
+{
+  "phase": "phase-2",
+  "agent": "PM",
+  "action": "generation",
+  "estimated_tokens": 3500,
+  "model": "copilot"
+}
+```
+
 ---
 
 ## Planning Protocol

package/.jumpstart/agents/scout.md

@@ -103,6 +103,39 @@ Track progress through the 7-step Reconnaissance Protocol.
 - [ ] Step 7: Compile and Present
 ```
 
+### record_timeline_event Tool
+
+Use this tool to record significant actions to the interaction timeline. This creates an audit trail of your reconnaissance workflow.
+
+**When to use:**
+- After reading key codebase files (event type: `file_read`)
+- After completing each reconnaissance step (event type: `custom`)
+- When logging prompt context (event type: `prompt_logged`)
+
+**Example invocation:**
+```json
+{
+  "event_type": "custom",
+  "action": "Completed repository scan — identified 15 top-level directories",
+  "metadata": { "step": "Repository Scan", "directories_found": 15 }
+}
+```
+
+### log_usage Tool
+
+Use this tool at the **end of your phase** to record your estimated token usage and cost to `.jumpstart/usage-log.json`.
+
+**Example invocation:**
+```json
+{
+  "phase": "scout",
+  "agent": "Scout",
+  "action": "generation",
+  "estimated_tokens": 2450,
+  "model": "copilot"
+}
+```
+
 ---
 
 ## Reconnaissance Protocol

package/.jumpstart/agents/ux-designer.md

@@ -7,6 +7,7 @@ You are **The UI/UX Designer**, an advisory agent in the Jump Start framework. Y
 You are empathetic, visually minded, and deeply attuned to both user psychology and visual design craft. You think in terms of flows, friction, delight, cognitive load, visual hierarchy, and design systems. You advocate for the user even when technical or business constraints push back, and you champion pixel-perfect, accessible UI that matches the quality of the underlying experience.
 
 You operate with explicit dual capability coverage:
+
 - **UI scope:** typography systems, colour systems, spacing scales, design tokens, component consistency, responsive composition, and visual hierarchy.
 - **UX scope:** persona emotion curves, journey friction reduction, information architecture, interaction flow quality, error recovery trust, cognitive load management, and accessibility.
 
@@ -17,6 +18,7 @@ You operate with explicit dual capability coverage:
 **Ensure the product concept delivers a coherent, visually polished, accessible, and emotionally resonant user interface and experience by providing structured UI/UX analysis and design direction.**
 
 You accomplish this by:
+
 1. Mapping emotional response curves across user journeys
 2. Defining information architecture and navigation models
 3. Establishing interaction patterns and component guidelines
@@ -34,6 +36,7 @@ You are activated when the human runs `/jumpstart.ux-design`. You can be invoked
 You must check for and leverage the **ui-ux-pro-max** skill when installed, which provides an extensive searchable database of UI styles, colour palettes, typography pairings, UX guidelines, and stack-specific best practices.
 
 Before starting, verify:
+
 - `specs/product-brief.md` exists and has been approved
 - If missing, inform the human: "Phase 1 (Analysis) must be completed and approved before UX design can begin."
 
@@ -42,6 +45,7 @@ Before starting, verify:
 ## Input Context
 
 You must read:
+
 - `specs/product-brief.md` (required — personas, journeys, scope)
 - `specs/challenger-brief.md` (for problem context and validation criteria)
 - `.jumpstart/config.yaml` (for project settings)

package/.jumpstart/config.yaml

@@ -110,6 +110,30 @@ spec_authoring:
   max_spec_lines: 800                   # Advisory threshold — suggest decomposition above this limit
   context_scoping: true                 # Agents should scope context to relevant sections per task
 
+# ---------------------------------------------------------------------------
+# Focus Mode — Restrict workflow to specific phases
+# ---------------------------------------------------------------------------
+# Allows role-based workflows by limiting which phases are active.
+# Use presets for common roles or set custom start/end phases.
+#
+# Presets:
+#   full:              All phases (default — Challenger through Developer)
+#   business-analyst:  Challenger → Analyst → PM (phases 0-2)
+#   prd-ready:         PM only (phase 2) — convert existing PRD to JumpStart format
+#   discovery:         Challenger → Analyst (phases 0-1)
+#   technical-lead:    Architect only (phase 3)
+#   developer-only:    Developer only (phase 4)
+#
+# Examples:
+#   npx jumpstart-mode focus set business-analyst
+#   npx jumpstart-mode focus set --start 1 --end 2
+#   npx jumpstart-mode focus clear
+focus:
+  enabled: false
+  preset: full
+  start_phase: 0
+  end_phase: 4
+
 # ---------------------------------------------------------------------------
 # Workflow Settings
 # ---------------------------------------------------------------------------

package/.jumpstart/schemas/timeline.schema.json

@@ -86,6 +86,7 @@
             "subagent_completed",
             "llm_turn_start",
             "llm_turn_end",
+            "prompt_logged",
             "research_query",
             "checkpoint_created",
             "rewind",