shipquick 1.0.0

package/_bmad-safe/bmm-safe/templates/safe/pi-objectives-template.md

@@ -0,0 +1,75 @@
+# SAFe PI Objectives Template
+
+## PI Information
+
+| Field           | Value                     |
+| --------------- | ------------------------- |
+| **PI Name**     | [AXP PI XX.X]             |
+| **ART Name**    | [ART Name]                |
+| **Team Name**   | [Team Name]               |
+| **PI Duration** | [Start Date] - [End Date] |
+
+---
+
+## Team PI Objectives
+
+### Committed Objectives
+
+| #   | Objective (SMART)                                                   | Business Value (1-10) | Features     |
+| --- | ------------------------------------------------------------------- | --------------------- | ------------ |
+| 1   | [Specific, Measurable, Achievable, Realistic, Time-bound objective] |                       | [F123, F124] |
+| 2   |                                                                     |                       |              |
+| 3   |                                                                     |                       |              |
+| 4   |                                                                     |                       |              |
+| 5   |                                                                     |                       |              |
+
+**Total Committed Business Value:** [Sum]
+
+### Uncommitted Objectives
+
+| #   | Objective                             | Business Value | Risk/Notes        |
+| --- | ------------------------------------- | -------------- | ----------------- |
+| 1   | [Stretch goal or high-risk objective] |                | [Why uncommitted] |
+| 2   |                                       |                |                   |
+
+**Total Uncommitted Business Value:** [Sum]
+
+---
+
+## SMART Objective Checklist
+
+Each objective should be:
+
+- [ ] **S**pecific - Clear and well-defined
+- [ ] **M**easurable - Can be objectively verified
+- [ ] **A**chievable - Within team's capacity
+- [ ] **R**ealistic - Considers dependencies and risks
+- [ ] **T**ime-bound - Will be completed within the PI
+
+---
+
+## Confidence Vote
+
+| Vote | Meaning                           |
+| ---- | --------------------------------- |
+| 5    | Highly confident, no concerns     |
+| 4    | Confident with minor concerns     |
+| 3    | Some doubts, need discussion      |
+| 2    | Significant concerns              |
+| 1    | Cannot commit to these objectives |
+
+**Team Confidence Vote:** [Average Score]
+
+---
+
+## Dependencies
+
+| Dependency | Provider Team | Needed By   | Status                               |
+| ---------- | ------------- | ----------- | ------------------------------------ |
+|            |               | Iteration X | [Identified / Confirmed / Delivered] |
+
+---
+
+## Notes
+
+[Additional context about objectives, assumptions, or constraints]

package/_bmad-safe/bmm-safe/templates/safe/roam-risk-template.md

@@ -0,0 +1,87 @@
+# SAFe ROAM Risk Template
+
+## PI Information
+
+| Field            | Value         |
+| ---------------- | ------------- |
+| **PI Name**      | [AXP PI XX.X] |
+| **ART Name**     | [ART Name]    |
+| **Last Updated** | [Date]        |
+
+---
+
+## ROAM Categories
+
+| Category          | Description                                                        |
+| ----------------- | ------------------------------------------------------------------ |
+| **R - Resolved**  | Risk has been addressed; no longer a concern                       |
+| **O - Owned**     | Someone has taken responsibility to handle it                      |
+| **A - Accepted**  | Nothing more can be done; if it occurs, release may be compromised |
+| **M - Mitigated** | Team has a plan to adjust if the risk occurs                       |
+
+---
+
+## PI Risks
+
+### Risk #1
+
+| Field                 | Value                 |
+| --------------------- | --------------------- |
+| **Risk Description**  | [Describe the risk]   |
+| **ROAM Category**     | [R / O / A / M]       |
+| **Owner**             | [Name]                |
+| **Impact**            | [High / Medium / Low] |
+| **Probability**       | [High / Medium / Low] |
+| **Affected Features** | [F123, F124]          |
+
+**Mitigation Plan:**
+[If Mitigated or Owned, describe the plan]
+
+---
+
+### Risk #2
+
+| Field                 | Value |
+| --------------------- | ----- |
+| **Risk Description**  |       |
+| **ROAM Category**     |       |
+| **Owner**             |       |
+| **Impact**            |       |
+| **Probability**       |       |
+| **Affected Features** |       |
+
+**Mitigation Plan:**
+
+---
+
+### Risk #3
+
+| Field                 | Value |
+| --------------------- | ----- |
+| **Risk Description**  |       |
+| **ROAM Category**     |       |
+| **Owner**             |       |
+| **Impact**            |       |
+| **Probability**       |       |
+| **Affected Features** |       |
+
+**Mitigation Plan:**
+
+---
+
+## Risk Summary
+
+| ROAM      | Count | Details |
+| --------- | ----- | ------- |
+| Resolved  |       |         |
+| Owned     |       |         |
+| Accepted  |       |         |
+| Mitigated |       |         |
+
+**Total Risks:** [Count]
+
+---
+
+## Review Notes
+
+[Notes from risk review session]

package/_bmad-safe/bmm-safe/templates/safe/story-template.md

@@ -0,0 +1,78 @@
+# SAFe User Story Template (Rally-Aligned)
+
+## Basic Information
+
+| Field                        | Value                                                          |
+| ---------------------------- | -------------------------------------------------------------- |
+| **Name**                     | [Story Name - Required]                                        |
+| **Bead ID**                  | US-F[n]-[Auto:NN]                                              |
+| **Parent Feature Bead**      | F-C[n]-[NN]                                                    |
+| **Portfolio Item (Feature)** | [F123: Feature Name]                                           |
+| **Schedule State**           | [Being Groomed / Defined / In-Progress / Completed / Accepted] |
+| **Plan Estimate**            | [Story Points]                                                 |
+| **Owner**                    | [username@example.com]                                         |
+
+## User Story
+
+**As a** [user role/persona],  
+**I want** [activity/functionality],  
+**so that** [business value/benefit].
+
+## Description
+
+[Detailed description of the story]
+
+## Enabler Classification
+
+| Field                   | Value                                                                               |
+| ----------------------- | ----------------------------------------------------------------------------------- |
+| **Enabler / Tech Debt** | [None / Exploration / Architectural / Infrastructure / Compliance / Technical Debt] |
+| **Ready**               | [True / False]                                                                      |
+| **Expedite**            | [True / False]                                                                      |
+
+## Estimation & Planning
+
+| Field             | Value                                    |
+| ----------------- | ---------------------------------------- |
+| **Plan Estimate** | [Story Points: 1, 2, 3, 5, 8, 13]        |
+| **Due Date**      | [MM/dd/yyyy]                             |
+| **Kanban State**  | [Backlog / Analysis / Dev / Test / Done] |
+
+## Acceptance Criteria
+
+### Scenario 1: [Happy Path]
+
+- **Given** [precondition]
+- **When** [action]
+- **Then** [expected result]
+
+### Scenario 2: [Edge Case]
+
+- **Given** [precondition]
+- **When** [action]
+- **Then** [expected result]
+
+### Scenario 3: [Error Handling]
+
+- **Given** [precondition]
+- **When** [action]
+- **Then** [expected result]
+
+## INVEST Checklist
+
+- [ ] **I**ndependent - Can be developed separately
+- [ ] **N**egotiable - Details can be discussed
+- [ ] **V**aluable - Delivers user/business value
+- [ ] **E**stimable - Can be sized
+- [ ] **S**mall - Fits in one iteration
+- [ ] **T**estable - Has clear acceptance criteria
+
+## Tasks
+
+| Task | Owner | Estimate | Status |
+| ---- | ----- | -------- | ------ |
+|      |       |          |        |
+
+## Notes
+
+[Additional context, dependencies, or technical notes]

package/_bmad-safe/bmm-safe/templates/safe/task-template.md

@@ -0,0 +1,43 @@
+# SAFe Task Template (Rally-Aligned)
+
+## Basic Information
+
+| Field                    | Value                               |
+| ------------------------ | ----------------------------------- |
+| **Name**                 | [Task Name - Required]              |
+| **Bead ID**              | TK-S[n]-[Auto:NN]                   |
+| **Parent Story Bead**    | US-F[n]-[NN]                        |
+| **Work Product (Story)** | [US123: Story Name - Required]      |
+| **State**                | [Defined / In-Progress / Completed] |
+| **Owner**                | [username@example.com]              |
+
+## Description
+
+[Describe what needs to be done to complete this task]
+
+## Time Tracking
+
+| Field        | Value             |
+| ------------ | ----------------- |
+| **Estimate** | [Hours]           |
+| **To Do**    | [Hours remaining] |
+| **Actuals**  | [Hours spent]     |
+
+## Task Details
+
+| Field              | Value                     |
+| ------------------ | ------------------------- |
+| **Blocked**        | [True / False]            |
+| **Blocked Reason** | [If blocked, explain why] |
+| **Ready**          | [True / False]            |
+| **Expedite**       | [True / False]            |
+
+## Completion Criteria
+
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+
+## Notes
+
+[Technical notes, approach, or references]

package/_bmad-safe/bmm-safe/templates/safe/theme-template.md

@@ -0,0 +1,55 @@
+# SAFe Theme Template (Rally-Aligned)
+
+## Basic Information
+
+| Field                   | Value                                           |
+| ----------------------- | ----------------------------------------------- |
+| **Name**                | [Theme Name - Required]                         |
+| **Bead ID**             | T-[Auto:NNN]                                    |
+| **Portfolio Item Type** | Theme                                           |
+| **State**               | [Discovering / Analyzing / Implementing / Done] |
+| **Owner**               | [username@example.com]                          |
+| **Display Color**       | [#hexcode]                                      |
+
+## Description
+
+[Describe the strategic theme and its business context]
+
+## Strategic Alignment
+
+| Field                   | Value                                                        |
+| ----------------------- | ------------------------------------------------------------ |
+| **Enterprise Outcome**  | [Efficiency / Growth / Customer Experience / Risk Reduction] |
+| **Investment Category** | [Business Health / Strategic Investment / Innovation]        |
+| **Line of Business**    | [LOB Name]                                                   |
+| **Priority Tier**       | [Tier 1 / Tier 2 / Tier 3]                                   |
+
+## WSJF Prioritization
+
+| Component                                   | Score (1-20)                | Notes                                       |
+| ------------------------------------------- | --------------------------- | ------------------------------------------- |
+| **User/Business Value**                     |                             | [Revenue impact? Customer satisfaction?]    |
+| **Time Criticality**                        |                             | [Fixed deadline? Decay of value?]           |
+| **Risk Reduction / Opportunity Enablement** |                             | [Future risk reduction? New opportunities?] |
+| **Job Size**                                |                             | [Relative effort estimate]                  |
+| **WSJF Score**                              | [Auto: (BV + TC + RR) / JS] |                                             |
+
+## Planning
+
+| Field                   | Value         |
+| ----------------------- | ------------- |
+| **PI Start Name**       | [AXP PI XX.X] |
+| **PI Finish Name**      | [AXP PI XX.X] |
+| **Planned Start Date**  | [MM/dd/yyyy]  |
+| **Planned End Date**    | [MM/dd/yyyy]  |
+| **Target Go Live Date** | [MM/dd/yyyy]  |
+
+## Acceptance Criteria
+
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+
+## Notes
+
+[Additional context or reference information]

package/_bmad-safe/bmm-safe/templates/safe/wsjf-calculator.md

@@ -0,0 +1,94 @@
+# SAFe WSJF Calculator
+
+## Overview
+
+**WSJF (Weighted Shortest Job First)** prioritizes work to produce maximum economic benefit.
+
+**Formula:** `WSJF = Cost of Delay (CoD) / Job Size`
+
+Where: `CoD = User/Business Value + Time Criticality + RR/OE`
+
+---
+
+## Scoring Guide
+
+Use relative Fibonacci numbers: **1, 2, 3, 5, 8, 13, 20**
+
+### User/Business Value
+
+| Score | Meaning                 |
+| ----- | ----------------------- |
+| 1     | Minimal value           |
+| 3     | Some value              |
+| 5     | Moderate value          |
+| 8     | High value              |
+| 13    | Very high value         |
+| 20    | Critical business value |
+
+### Time Criticality
+
+| Score | Meaning                             |
+| ----- | ----------------------------------- |
+| 1     | No deadline, customers will wait    |
+| 3     | Preferred timeline                  |
+| 5     | Delay causes moderate impact        |
+| 8     | Fixed deadline approaching          |
+| 13    | Urgent, significant decay           |
+| 20    | Immediate, major penalty if delayed |
+
+### Risk Reduction / Opportunity Enablement (RR/OE)
+
+| Score | Meaning                              |
+| ----- | ------------------------------------ |
+| 1     | No risk reduction or new opportunity |
+| 3     | Minor risk reduction                 |
+| 5     | Moderate risk/opportunity            |
+| 8     | Significant enablement               |
+| 13    | High strategic value                 |
+| 20    | Critical for future work             |
+
+### Job Size (Duration/Effort)
+
+| Score | Meaning               |
+| ----- | --------------------- |
+| 1     | Very small (1 sprint) |
+| 2     | Small (1-2 sprints)   |
+| 3     | Medium (1 PI)         |
+| 5     | Large (1-2 PIs)       |
+| 8     | Very large (2-3 PIs)  |
+| 13    | Extra large (3+ PIs)  |
+
+---
+
+## Backlog Prioritization
+
+| Item      | BV  | TC  | RR/OE | CoD   | Job Size | WSJF     | Priority |
+| --------- | --- | --- | ----- | ----- | -------- | -------- | -------- |
+| [Item 1]  |     |     |       | [Sum] |          | [CoD/JS] |          |
+| [Item 2]  |     |     |       |       |          |          |          |
+| [Item 3]  |     |     |       |       |          |          |          |
+| [Item 4]  |     |     |       |       |          |          |          |
+| [Item 5]  |     |     |       |       |          |          |          |
+| [Item 6]  |     |     |       |       |          |          |          |
+| [Item 7]  |     |     |       |       |          |          |          |
+| [Item 8]  |     |     |       |       |          |          |          |
+| [Item 9]  |     |     |       |       |          |          |          |
+| [Item 10] |     |     |       |       |          |          |          |
+
+---
+
+## Calculation Steps
+
+1. **Score each CoD component** (BV, TC, RR/OE) using relative Fibonacci
+2. **Sum CoD components** → Total Cost of Delay
+3. **Estimate Job Size** using relative sizing
+4. **Calculate WSJF** = CoD ÷ Job Size
+5. **Prioritize** highest WSJF first
+
+---
+
+## Notes
+
+- Always use **relative** scoring (compare items to each other)
+- Recalculate when new items are added
+- Review WSJF before each PI Planning

package/_bmad-safe/bmm-safe/workflows/1-analysis/create-product-brief/product-brief.template.md

@@ -0,0 +1,10 @@
+---
+stepsCompleted: []
+inputDocuments: []
+date: { system-date }
+author: { user }
+---
+
+# Product Brief: {{project_name}}
+
+<!-- Content will be appended sequentially through collaborative workflow steps -->

package/_bmad-safe/bmm-safe/workflows/1-analysis/create-product-brief/steps/step-01-init.md

@@ -0,0 +1,177 @@
+---
+name: 'step-01-init'
+description: 'Initialize the product brief workflow by detecting continuation state and setting up the document'
+
+# File References
+nextStepFile: './step-02-vision.md'
+outputFile: '{planning_artifacts}/product-brief-{{project_name}}-{{date}}.md'
+
+# Template References
+productBriefTemplate: '../product-brief.template.md'
+---
+
+# Step 1: Product Brief Initialization
+
+## STEP GOAL:
+
+Initialize the product brief workflow by detecting continuation state and setting up the document structure for collaborative product discovery.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are a product-focused Business Analyst facilitator
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
+- ✅ Maintain collaborative discovery tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on initialization and setup - no content generation yet
+- 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them
+- 💬 Approach: Systematic setup with clear reporting to user
+- 📋 Detect existing workflow state and handle continuation properly
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Show your analysis of current state before taking any action
+- 💾 Initialize document structure and update frontmatter appropriately
+- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
+- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue)
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Variables from workflow.md are available in memory
+- Focus: Workflow initialization and document setup only
+- Limits: Don't assume knowledge from other steps or create content yet
+- Dependencies: Configuration loaded from workflow.md initialization
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Check for Existing Workflow State
+
+First, check if the output document already exists:
+
+**Workflow State Detection:**
+
+- Look for file `{outputFile}`
+- If exists, read the complete file including frontmatter
+- If not exists, this is a fresh workflow
+
+### 2. Handle Continuation (If Document Exists)
+
+If the document exists and has frontmatter with `stepsCompleted`:
+
+**Continuation Protocol:**
+
+- **STOP immediately** and load `./step-01b-continue.md`
+- Do not proceed with any initialization tasks
+- Let step-01b handle all continuation logic
+- This is an auto-proceed situation - no user choice needed
+
+### 3. Fresh Workflow Setup (If No Document)
+
+If no document exists or no `stepsCompleted` in frontmatter:
+
+#### A. Input Document Discovery
+
+load context documents using smart discovery. Documents can be in the following locations:
+- {planning_artifacts}/**
+- {output_folder}/**
+- {product_knowledge}/**
+- docs/**
+
+Also - when searching - documents can be a single markdown file, or a folder with an index and multiple files. For Example, if searching for `*foo*.md` and not found, also search for a folder called *foo*/index.md (which indicates sharded content)
+
+Try to discover the following:
+- Brainstorming Reports (`*brainstorming*.md`)
+- Research Documents (`*research*.md`)
+- Project Documentation (generally multiple documents might be found for this in the `{product_knowledge}` or `docs` folder.)
+- Project Context (`**/project-context.md`)
+
+<critical>Confirm what you have found with the user, along with asking if the user wants to provide anything else. Only after this confirmation will you proceed to follow the loading rules</critical>
+
+**Loading Rules:**
+
+- Load ALL discovered files completely that the user confirmed or provided (no offset/limit)
+- If there is a project context, whatever is relevant should try to be biased in the remainder of this whole workflow process
+- For sharded folders, load ALL files to get complete picture, using the index first to potentially know the potential of each document
+- index.md is a guide to what's relevant whenever available
+- Track all successfully loaded files in frontmatter `inputDocuments` array
+
+#### B. Create Initial Document
+
+**Document Setup:**
+
+- Copy the template from `{productBriefTemplate}` to `{outputFile}`, and update the frontmatter fields
+
+#### C. Present Initialization Results
+
+**Setup Report to User:**
+"Welcome {{user_name}}! I've set up your product brief workspace for {{project_name}}.
+
+**Document Setup:**
+
+- Created: `{outputFile}` from template
+- Initialized frontmatter with workflow state
+
+**Input Documents Discovered:**
+
+- Research: {number of research files loaded or "None found"}
+- Brainstorming: {number of brainstorming files loaded or "None found"}
+- Project docs: {number of project files loaded or "None found"}
+- Project Context: {number of project context files loaded or "None found"}
+
+**Files loaded:** {list of specific file names or "No additional documents found"}
+
+Do you have any other documents you'd like me to include, or shall we continue to the next step?"
+
+### 4. Present MENU OPTIONS
+
+Display: "**Proceeding to product vision discovery...**"
+
+#### Menu Handling Logic:
+
+- After setup report is presented, without delay, read fully and follow: {nextStepFile}
+
+#### EXECUTION RULES:
+
+- This is an initialization step with auto-proceed after setup completion
+- Proceed directly to next step after document setup and reporting
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN [setup completion is achieved and frontmatter properly updated], will you then read fully and follow: `{nextStepFile}` to begin product vision discovery.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Existing workflow detected and properly handed off to step-01b
+- Fresh workflow initialized with template and proper frontmatter
+- Input documents discovered and loaded using sharded-first logic
+- All discovered files tracked in frontmatter `inputDocuments`
+- Menu presented and user input handled correctly
+- Frontmatter updated with `stepsCompleted: [1]` before proceeding
+
+### ❌ SYSTEM FAILURE:
+
+- Proceeding with fresh initialization when existing workflow exists
+- Not updating frontmatter with discovered input documents
+- Creating document without proper template structure
+- Not checking sharded folders first before whole files
+- Not reporting discovered documents to user clearly
+- Proceeding without user selecting 'C' (Continue)
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.