jumpstart-mode 1.1.13 → 1.1.14

package/.jumpstart/skills/jira-delivery-builder/templates/mvp-backlog-template.md

@@ -0,0 +1,39 @@
+# MVP Backlog Template
+
+## Initiative
+
+[Initiative Name]
+
+## Epics
+
+1. [Epic Name]
+2. [Epic Name]
+
+## Sprint 0
+
+- [Spike]
+- [Environment setup task]
+- [Access dependency task]
+
+## Sprint 1
+
+- [Story]
+- [Task]
+
+## Sprint 2
+
+- [Story]
+- [Task]
+
+## Sprint 3
+
+- [Story]
+- [Hardening task]
+
+## Risks
+
+- [Risk]
+
+## Client Dependencies
+
+- [Dependency]

package/.jumpstart/skills/jira-delivery-builder/templates/review-queue-story-template.md

@@ -0,0 +1,22 @@
+# Review Queue Story Template
+
+## User Story
+
+As a [reviewer], I want to see AI output with evidence and status controls so that I can approve, reject, or correct with confidence.
+
+## Acceptance Criteria
+
+1. Given queued items, when the reviewer opens the queue, then items display status, confidence, and source evidence.
+2. Given a reviewer decision, when approve or reject is selected, then reason and actor are recorded.
+3. Given a corrected output, when submitted, then the updated value is traceable in audit history.
+4. Given queue loading errors, when failures occur, then the UI shows recoverable error states.
+
+## Dependencies
+
+- review API
+- identity and role mapping
+
+## Source Traceability
+
+- Source: [Reference]
+- Confidence: [Source-backed or derived from user instruction]

package/.jumpstart/skills/jira-delivery-builder/templates/spike-template.md

@@ -0,0 +1,29 @@
+# Spike Template
+
+## Objective
+
+[Unknown to validate]
+
+## Questions To Answer
+
+- [Question]
+- [Question]
+- [Question]
+
+## Timebox
+
+[1-2 days recommended]
+
+## Deliverable
+
+[Design note, benchmark report, recommendation]
+
+## Exit Criteria
+
+- [Decision-ready output produced]
+- [Risks and options documented]
+
+## Source Traceability
+
+- Source: [Reference]
+- Confidence: [Source-backed or derived from user instruction]

package/.jumpstart/skills/jira-delivery-builder/templates/sprint-readiness-report.md

@@ -0,0 +1,26 @@
+# Sprint Readiness Report
+
+## Summary
+
+- Total issues reviewed: [N]
+- Ready for sprint planning: [N]
+- Not ready: [N]
+- Blocked by external dependency: [N]
+
+## Ready Issues
+
+- [Issue Key] [Summary]
+
+## Not Ready Issues And Gaps
+
+- [Issue Key] [Gap]
+
+## Blocking Dependencies
+
+- [Dependency] [Owner] [Needed By] [Risk]
+
+## Recommendations
+
+1. [Action]
+2. [Action]
+3. [Action]

package/.jumpstart/skills/jira-delivery-builder/templates/technical-task-template.md

@@ -0,0 +1,34 @@
+# Technical Task Template
+
+## Summary
+
+[Technical implementation objective]
+
+## Context
+
+[Why this technical work is needed]
+
+## Scope
+
+- [Implementation item]
+- [Implementation item]
+
+## Acceptance Criteria
+
+1. Given [technical context], when [implementation is complete], then [verifiable outcome].
+2. Given [failure condition], when [error occurs], then [expected behavior].
+
+## Nonfunctional Requirements
+
+- security
+- observability
+- performance
+
+## Dependencies
+
+- [Dependency]
+
+## Source Traceability
+
+- Source: [Reference]
+- Confidence: [Source-backed or derived from user instruction]

package/.jumpstart/skills/jira-delivery-builder/templates/user-story-template.md

@@ -0,0 +1,33 @@
+# User Story Template
+
+## User Story
+
+As a [role], I want [capability], so that [business outcome].
+
+## Background
+
+[Context from source material]
+
+## Acceptance Criteria
+
+1. Given [context], when [action], then [expected result].
+2. Given [context], when [action], then [expected result].
+3. Given [error or edge case], when [action], then [handling].
+
+## Implementation Notes
+
+[Constraints, assumptions, architecture notes]
+
+## Dependencies
+
+- [Dependency]
+
+## Out Of Scope
+
+- [Exclusion]
+
+## Source Traceability
+
+- Source: [Reference]
+- Requirement ID: [Optional]
+- Confidence: [Source-backed or derived from user instruction]

package/.jumpstart/skills/jira-delivery-operations/README.md

@@ -0,0 +1,10 @@
+# Jira Delivery Operations
+
+This skill coordinates the full Jira delivery lifecycle for AI Innovation Pod and JumpStart workflows.
+
+## Typical workflow
+
+1. Build backlog from source material
+2. Normalize backlog to IU and Pod tier fit
+3. Validate requirement coverage and traceability
+4. Run recurring delivery status and sprint readiness reporting

package/.jumpstart/skills/jira-delivery-operations/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: jira-delivery-operations
+description: Coordinate end-to-end Jira delivery operations for AI Innovation Pod and JumpStart work by routing between backlog creation, Innovation Unit normalization, PRD-to-Jira traceability validation, and ongoing status reporting. Use when the user asks for a complete workflow rather than a single Jira artifact.
+---
+
+# Jira Delivery Operations
+
+Use this skill as an orchestrator when the user needs a full Jira delivery operating loop across planning, sizing, validation, and reporting.
+
+This skill should route to specialized Jira skills instead of duplicating their work.
+
+## Route targets
+
+- `jira-delivery-builder` for backlog generation and issue decomposition
+- `jira-innovation-unit-normalizer` for IU sizing and Pod tier fit
+- `prd-to-jira-traceability-validator` for requirement coverage and traceability checks
+- `jira-pod-status-reporter` for delivery reporting and sprint readiness updates
+
+## Use this for
+
+- end-to-end Jira delivery setup from source documents
+- backlog-to-capacity workflow design
+- pre-sprint readiness checks combining coverage and dependencies
+- ongoing Pod reporting cadence setup
+- packaging delivery operations guidance for client-safe execution
+
+## Do not use this for
+
+- single-surface asks that are already covered by one specialized skill
+- direct Confluence/Jira API execution details when the user only needs one report; route to `atlassian-generate-status-report`
+
+## Orchestration workflow
+
+1. Classify the user ask into one of four phases: build, normalize, validate, report.
+2. Determine the minimum required outputs for the current phase.
+3. Route to the specialized skill for that phase.
+4. If the ask spans phases, produce a phased execution checklist with outputs, owners, and readiness gates.
+5. Maintain traceability and dependency visibility across phases.
+
+## Phase outputs
+
+- Build phase:
+  - Jira issue hierarchy
+  - acceptance criteria
+  - dependency register
+- Normalize phase:
+  - IU-sized backlog table
+  - tier fit and wallet pressure notes
+- Validate phase:
+  - requirement coverage summary
+  - uncovered requirement list
+  - weak trace list
+- Report phase:
+  - weekly status report
+  - sprint readiness summary
+
+## Bundled resources
+
+- Read `./references/routing-matrix.md` for phase-to-skill decisions.
+- Read `./references/operating-playbook.md` for cadence recommendations.
+- Use `./templates/phase-checklist.md` for phased execution.
+- Use `./templates/weekly-operations-cadence.md` for recurring workflow setup.
+- Use `./evals/eval-cases.md` to validate routing quality.
+
+## Quality rules
+
+- avoid running all phases when the user asks for only one
+- keep outputs explicit, bounded, and testable
+- preserve source traceability between phases
+- call out dependencies that block downstream phases

package/.jumpstart/skills/jira-delivery-operations/evals/README.md

@@ -0,0 +1,3 @@
+# Jira Delivery Operations Evals
+
+Use these cases to verify that the orchestrator routes correctly and does not overrun scope.

package/.jumpstart/skills/jira-delivery-operations/evals/eval-cases.md

@@ -0,0 +1,13 @@
+# Eval Cases
+
+## Case 1: Backlog-only ask
+
+Pass when the orchestrator routes only to backlog generation and does not force IU or reporting outputs.
+
+## Case 2: End-to-end setup ask
+
+Pass when the orchestrator emits a phased checklist with build, normalize, validate, and report outputs.
+
+## Case 3: Status-only ask
+
+Pass when the orchestrator routes to reporting without reopening backlog decomposition.

package/.jumpstart/skills/jira-delivery-operations/references/operating-playbook.md

@@ -0,0 +1,21 @@
+# Operating Playbook
+
+## Suggested cadence
+
+- Weekly planning:
+  - refine backlog
+  - review dependencies
+  - confirm sprint-ready cut line
+- Mid-week execution check:
+  - update blocker register
+  - update risk summary
+- End-of-week review:
+  - publish status report
+  - update traceability gaps
+
+## Stage gates
+
+- Gate 1: backlog structure complete
+- Gate 2: IU normalization complete for active scope
+- Gate 3: requirement coverage acceptable
+- Gate 4: status and readiness reporting operational

package/.jumpstart/skills/jira-delivery-operations/references/routing-matrix.md

@@ -0,0 +1,9 @@
+# Routing Matrix
+
+| User ask pattern | Route skill |
+| --- | --- |
+| Convert notes or PRD into Jira issues | jira-delivery-builder |
+| Size Jira backlog in IUs | jira-innovation-unit-normalizer |
+| Validate requirement coverage against Jira | prd-to-jira-traceability-validator |
+| Produce weekly or sprint status | jira-pod-status-reporter |
+| End-to-end delivery flow | jira-delivery-operations |

package/.jumpstart/skills/jira-delivery-operations/templates/phase-checklist.md

@@ -0,0 +1,25 @@
+# Jira Delivery Operations Checklist
+
+## Build
+
+- [ ] backlog hierarchy drafted
+- [ ] acceptance criteria testable
+- [ ] dependencies captured
+
+## Normalize
+
+- [ ] IU sizing complete for active backlog
+- [ ] tier fit reviewed
+- [ ] split recommendations captured
+
+## Validate
+
+- [ ] requirement coverage reviewed
+- [ ] uncovered requirements triaged
+- [ ] weak trace issues remediated
+
+## Report
+
+- [ ] weekly report prepared
+- [ ] sprint readiness updated
+- [ ] blockers and client dependencies escalated

package/.jumpstart/skills/jira-delivery-operations/templates/weekly-operations-cadence.md

@@ -0,0 +1,7 @@
+# Weekly Operations Cadence
+
+| Day | Activity | Primary Output |
+| --- | --- | --- |
+| Monday | Backlog refinement and dependency review | Updated sprint candidate scope |
+| Wednesday | Execution and blocker check | Updated risk and dependency view |
+| Friday | Status and readiness report | Sponsor-ready weekly update |

package/.jumpstart/skills/jira-innovation-unit-normalizer/README.md

@@ -0,0 +1,10 @@
+# Jira Innovation Unit Normalizer
+
+This skill translates Jira backlog items into Innovation Unit sizing guidance for AI Innovation Pod planning.
+
+## Typical outputs
+
+- IU-sized backlog table
+- Tier-fit recommendation
+- Wallet burn summary
+- Split recommendations for oversized stories

package/.jumpstart/skills/jira-innovation-unit-normalizer/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: jira-innovation-unit-normalizer
+description: Normalize Jira backlogs into Innovation Unit sizing views for AI Innovation Pod planning. Use this skill when the user wants Jira epics, stories, tasks, spikes, or backlog exports translated into IU categories, complexity-adjusted sizing, tier fit, wallet burn, or month-by-month Pod capacity guidance.
+---
+
+# Jira Innovation Unit Normalizer
+
+Use this skill to convert Jira backlog items into Innovation Unit planning views.
+
+This skill bridges Jira execution artifacts and the AI Innovation Pod IU operating model. It is for capacity planning and demand shaping, not pricing commitments.
+
+## Use this for
+
+- sizing Jira backlog items in Innovation Units
+- mapping a Jira export to Ignition, Turbo, or Overdrive capacity
+- estimating wallet burn from existing epics and stories
+- creating a normalized backlog sizing table from Jira metadata
+- flagging backlog items that need splitting before reliable IU sizing
+
+## Do not use this for
+
+- creating Jira tickets; use `jira-delivery-builder`
+- bottom-up hours or ROM estimation; use `bottom-up-estimation`
+- detailed IU scoping from rough notes without Jira structure; use `innovation-unit-estimator`
+
+## Bundled resources
+
+- Read `./references/normalization-rules.md` for Jira-to-IU mapping logic.
+- Read `./references/complexity-mapping.md` for Standard, Medium, and High triggers.
+- Use `./templates/jira-iu-estimate.md` for the narrative output.
+- Use `./templates/jira-iu-backlog.csv` for structured backlog rows.
+- Use `./scripts/normalize_jira_to_iu.py` when the user provides a Jira CSV export.
+- Use `./evals/eval-cases.md` for validation scenarios.
+
+Repository references that should guide interpretation:
+
+- `../../../04-deliver/engagement-management/innovation-units.md`
+- `../../../05-reference/ai-innovation-pod-tier-matrix.md`
+
+## Workflow
+
+1. Read the Jira backlog or structured issue list.
+2. Normalize issue types into delivery outcomes.
+3. Map each item to the nearest IU category.
+4. Apply visible complexity drivers.
+5. Produce a backlog sizing table and tier-fit view.
+6. Call out items that should be split or treated as dependency-bound.
+
+## Required output
+
+For substantial requests, include:
+
+- total estimated IUs
+- backlog sizing table
+- tier-fit assessment
+- complexity drivers
+- scope or sequencing recommendations
+
+## Quality rules
+
+- do not hide ambiguity; label assumptions
+- do not convert IU counts into hours by default
+- recommend splitting oversized or mixed-scope issues before sizing them as one unit
+- treat unresolved dependencies as calendar risk even if IU count appears to fit

package/.jumpstart/skills/jira-innovation-unit-normalizer/evals/README.md

@@ -0,0 +1,3 @@
+# Jira Innovation Unit Normalizer Evals
+
+Use these evals to ensure Jira issue shapes are converted into defensible IU planning outputs.

package/.jumpstart/skills/jira-innovation-unit-normalizer/evals/eval-cases.md

@@ -0,0 +1,16 @@
+# Eval Cases
+
+## Case 1: Mixed MVP backlog
+
+Pass when:
+
+- stories and tasks are sized separately
+- oversized epics are not treated as one implementation unit without warning
+- tier fit is stated
+
+## Case 2: Enterprise AI backlog
+
+Pass when:
+
+- compliance and legacy signals raise complexity
+- risks are called out separately from IU count

package/.jumpstart/skills/jira-innovation-unit-normalizer/references/complexity-mapping.md

@@ -0,0 +1,21 @@
+# Complexity Mapping
+
+## Standard
+
+- clean structured data
+- modern API integration
+- internal-only workflow
+
+## Medium
+
+- unstructured documents
+- custom business logic
+- role-based access controls
+- multiple system touchpoints
+
+## High
+
+- fragmented or low-quality source data
+- legacy integration constraints
+- strict compliance or enterprise controls
+- multiple approvals or high evaluation burden

package/.jumpstart/skills/jira-innovation-unit-normalizer/references/normalization-rules.md

@@ -0,0 +1,13 @@
+# Normalization Rules
+
+## Default mapping
+
+- Epic: size as grouped demand, not a direct implementation unit, unless it is already tightly bounded
+- Story: primary unit for user-facing implementation
+- Task: map to technical delivery categories such as connector, UI, observability, or hardening
+- Spike: map as discovery or uncertainty-reduction work
+- Bug: size only when materially scoped and reproducible
+
+## Outcome-first rule
+
+Map the issue to the nearest delivered capability, not just its issue type label.

package/.jumpstart/skills/jira-innovation-unit-normalizer/scripts/fixtures/README.md

@@ -0,0 +1,7 @@
+# Script Fixtures
+
+Use this sample to test Jira to IU normalization:
+
+```bash
+python scripts/normalize_jira_to_iu.py scripts/fixtures/sample-jira-backlog.csv
+```

package/.jumpstart/skills/jira-innovation-unit-normalizer/scripts/fixtures/sample-jira-backlog.csv

@@ -0,0 +1,5 @@
+Issue Type,Summary,Description
+Story,Build grounded answer endpoint,Implement retrieval and citation response behavior
+Task,Configure telemetry pipeline,Add prompt and model runtime logging
+Spike,Validate legacy ERP connector,Assess mainframe dependency risk and compliance constraints
+Story,Implement PDF chunking,Ingest pdf files with rbac filtering for secure retrieval

package/.jumpstart/skills/jira-innovation-unit-normalizer/scripts/normalize_jira_to_iu.py

@@ -0,0 +1,48 @@
+#!/usr/bin/env python3
+"""Normalize a Jira CSV export into simple IU sizing suggestions."""
+
+from __future__ import annotations
+
+import argparse
+import csv
+from pathlib import Path
+
+
+BASE_BY_TYPE = {
+    "story": 10,
+    "task": 5,
+    "spike": 5,
+    "bug": 5,
+    "epic": 20,
+}
+
+
+def multiplier_for_text(text: str) -> int:
+    lowered = text.lower()
+    if any(token in lowered for token in ("legacy", "phi", "pii", "compliance", "mainframe")):
+        return 8
+    if any(token in lowered for token in ("pdf", "rbac", "approval", "integration", "retrieval")):
+        return 3
+    return 1
+
+
+def main() -> None:
+    parser = argparse.ArgumentParser(description="Normalize Jira CSV rows into rough IU values.")
+    parser.add_argument("csv_path", type=Path)
+    args = parser.parse_args()
+
+    with args.csv_path.open("r", encoding="utf-8", newline="") as handle:
+        reader = csv.DictReader(handle)
+        writer = csv.writer(__import__("sys").stdout)
+        writer.writerow(["Summary", "Issue Type", "Base IUs", "Multiplier", "Sized IUs"])
+        for row in reader:
+            issue_type = (row.get("Issue Type") or "task").strip().lower()
+            summary = (row.get("Summary") or "").strip()
+            description = (row.get("Description") or "").strip()
+            base = BASE_BY_TYPE.get(issue_type, 5)
+            multiplier = multiplier_for_text(f"{summary} {description}")
+            writer.writerow([summary, issue_type, base, multiplier, base * multiplier])
+
+
+if __name__ == "__main__":
+    main()

package/.jumpstart/skills/jira-innovation-unit-normalizer/templates/jira-iu-backlog.csv

@@ -0,0 +1,2 @@
+ID,Jira Item,IU Category,Complexity,Sized IUs,Notes
+STORY-001,Example story,Basic RAG Workflow,Medium,60,Includes permission filtering and observability

package/.jumpstart/skills/jira-innovation-unit-normalizer/templates/jira-iu-estimate.md

@@ -0,0 +1,17 @@
+# Jira To IU Estimate
+
+## Summary
+
+- Total IUs: [N]
+- Confidence: [Low, Medium, High]
+- Recommended tier: [Ignition, Turbo, Overdrive]
+
+## Backlog Sizing Table
+
+| ID | Jira Item | IU Category | Complexity | Sized IUs | Notes |
+| --- | --- | --- | --- | ---: | --- |
+| [ID] | [Summary] | [Category] | [Level] | [N] | [Why] |
+
+## Tier Fit
+
+[Narrative on wallet fit, likely phasing, and risks]

package/.jumpstart/skills/jira-pod-status-reporter/README.md

@@ -0,0 +1,18 @@
+# Jira Pod Status Reporter
+
+This skill converts Jira issue state and backlog exports into AI Innovation Pod and JumpStart delivery reports.
+
+## Typical outputs
+
+- Weekly status report
+- Sprint readiness summary
+- Blocked work and dependency tracker
+- Epic progress report
+- Client-ready delivery narrative
+
+## Typical inputs
+
+- Jira issue queries or exports
+- Sprint backlog CSV
+- Epic status snapshots
+- Dependency labels and blocked issue lists