jumpstart-mode 1.1.13 → 1.1.14

package/.jumpstart/skills/win-theme-extractor/references/proof-mapping-matrix.md

@@ -0,0 +1,34 @@
+# Proof Mapping Matrix
+
+After selecting win themes, map them to sections and evidence so the drafting team knows how each theme gets earned.
+
+## Columns
+
+| Column | Purpose |
+| ------ | ------- |
+| Win Theme | The approved short theme statement |
+| Buyer Decision Driver | The fear, urgency, or criterion this theme addresses |
+| Proof Source | Case study, prior engagement, asset, delivery model, battlecard insight, or scoped commitment |
+| Proof Status | `confirmed`, `partial`, or `missing` |
+| Best Sections | Which sections should carry this theme |
+| Best Proof Placement | Where the proof should appear so the claim feels earned |
+| Watchouts | What not to imply or overclaim |
+
+## Example
+
+| Win Theme | Buyer Decision Driver | Proof Source | Proof Status | Best Sections | Best Proof Placement | Watchouts |
+| --------- | --------------------- | ------------ | ------------ | ------------- | -------------------- | --------- |
+| Bounded delivery with clear off-ramps | Fear of open-ended consulting spend | Tier matrix, fixed-fee examples, hybrid handoff logic | confirmed | Executive summary, pricing, path forward | Pricing intro plus one line in executive summary | Do not imply later phases are already agreed |
+| One team from discovery to delivery | Fear of rework and re-onboarding | Jump Start to Pod handoff pattern, named Pod roles | partial | Approach, differentiators | Approach overview and team model | Do not promise the same named staff unless confirmed |
+| Evaluation and governance from day one | Fear of unsafe AI pilot | Governance assets, evaluation language, controlled pilot pattern | confirmed | Differentiators, approach, assumptions | Approach section and governance callout | Avoid sounding like a full enterprise control program |
+
+## Placement Rules
+
+- Put proof as close as possible to the first place the theme is introduced.
+- Do not hide all proof in appendices.
+- Do not make pricing carry a theme that has never been established earlier.
+- If proof is partial or missing, either downgrade the theme or note the gap explicitly before drafting.
+
+## What To Drop
+
+If a theme has no clear section placement or no credible proof source, drop it. Good themes survive contact with section planning.

package/.jumpstart/skills/win-theme-extractor/references/win-theme-scorecard.md

@@ -0,0 +1,45 @@
+# Win Theme Scorecard
+
+Use this scorecard to rank candidate themes before they enter the proposal. The purpose is to shrink a long list of possible messages into a few defensible, buyer-relevant themes.
+
+## Scoring Scale
+
+Score each theme from 1 to 5 on each criterion.
+
+- **1 = weak**
+- **3 = moderate**
+- **5 = strong**
+
+## Criteria
+
+| Criterion | Question |
+| --------- | -------- |
+| Buyer relevance | Does this theme clearly connect to the buyer's top fear, urgency, or decision criterion? |
+| Differentiation | Does this theme help the team win a choice, not just sound competent? |
+| Proof strength | Do we have real proof, examples, assets, or commitments that earn this theme? |
+| Repeatability | Can this theme appear across multiple sections without becoming forced or repetitive? |
+| Commercial safety | Can we repeat this theme without implying unsold scope, risky claims, or liability? |
+| Motion fit | Does it reinforce the actual motion being sold: Jump Start, Pod, hybrid, or other? |
+| Memory value | Is this something the client is likely to remember after the read? |
+
+## Recommended Use
+
+- Prioritize themes with strong buyer relevance and proof strength over internally exciting but weakly evidenced messages.
+- Reject themes that require verbal explanation every time; they will not survive proposal drafting.
+- A theme with weak commercial safety should be downgraded even if it sounds persuasive.
+
+## Output Shape
+
+| Theme | Buyer Relevance | Differentiation | Proof Strength | Repeatability | Commercial Safety | Motion Fit | Memory Value | Total | Decision |
+| ----- | --------------- | --------------- | -------------- | ------------- | ----------------- | ---------- | ------------ | ----- | -------- |
+| Bounded pilot with explicit governance | 5 | 4 | 5 | 5 | 5 | 5 | 4 | 33 | Keep |
+
+## Decision Rules
+
+- **Keep**: high total and no score below 3 in Buyer relevance or Proof strength
+- **Keep with caution**: high total but one weak area that can be repaired
+- **Drop**: low total or weak proof / weak buyer relevance
+
+## Cap The Set
+
+Even if more themes score well, cap the final set at **3 to 5**. The proposal needs memory, not abundance.

package/.jumpstart/skills/work-breakdown-builder/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: work-breakdown-builder
+description: Create Excel work breakdown structure workbooks from notes, documents, meeting transcripts, workshop outputs, or audio-derived transcripts, especially for cloud infrastructure, platform setup, landing zone, DevSecOps, migration, and implementation planning. Use this skill whenever the user wants a WBS, project workbook, implementation plan workbook, staffing-and-hours workbook, Gantt workbook, infrastructure estimate workbook, or RFP response planning spreadsheet, even if they only provide rough notes or workshop transcripts. The output should be a structured `.xlsx` workbook modeled on a cloud infrastructure WBS example, with task breakdown, staffing recommendations, effort estimates, supporting roles, and a schedule view.
+---
+
+# Work Breakdown Builder
+
+Create a planning workbook that turns messy implementation input into an Excel work breakdown structure. The workbook is meant for Jump Start and AI Innovation Pod teams that need a reusable planning artifact for cloud infrastructure and adjacent implementation work.
+
+Use `ideas-to-create/work-breakdown-builder/Cloud Infrastructure WBS example.xlsx` as the primary style and structure reference whenever it is available. Inspect its sheet names, visible layout, formulas, role sheet, gantt behavior, and planning terminology before generating a new workbook. For safe internal reuse, start from the sanitized workbook at `references/Cloud Infrastructure WBS Template.xlsx` and its source data in `references/mock-wbs-data.json`.
+
+## When to Use This Skill
+
+Use this skill when the user needs to convert discovery notes, implementation workshops, architecture plans, transcripts, or RFP inputs into a project-planning workbook such as:
+
+- Work breakdown structure workbook.
+- Cloud infrastructure implementation plan workbook.
+- Gantt workbook with staffing and hours.
+- RFP planning workbook for landing zone, platform, DevSecOps, security, DR, or data platform setup.
+- Delivery-planning spreadsheet for Jump Start follow-on or AI Innovation Pod execution.
+
+Do not use this skill for generic workshop trackers, stakeholder workbooks, or business-only roadmaps when a WBS is not the main deliverable.
+
+## Inputs to Accept
+
+Work from any combination of:
+
+- Discovery notes, architecture notes, workshop notes, or rough bullets.
+- Meeting transcripts or audio transcripts.
+- RFP text, scope statements, proposal drafts, or technical requirement lists.
+- Existing project-plan spreadsheets or reference workbooks.
+- Uploaded documents describing cloud scope, environments, controls, or implementation phases.
+
+If the user gives audio without a transcript, transcribe first or ask for a transcript. Do not invent technical scope that is not supported by the source. Mark gaps as `TBD`, `Unknown`, or a labeled assumption.
+
+## Workbook Goal
+
+The output is a client-safe `.xlsx` workbook that organizes:
+
+- A task-level WBS.
+- Recommended staffing by role.
+- Estimated hours and weeks.
+- Security-specific effort where relevant.
+- A reusable roles sheet.
+- A schedule or gantt-style planning view.
+- A compact RFP/reference view for proposal shaping.
+
+## Expected Workbook Shape
+
+Model the output on the reference workbook with these sheets:
+
+- `WBS`
+- `Roles`
+- `Gantt Chart`
+- `RFP Reference`
+
+Read `references/wbs-structure.md` for the default column set, extraction rules, and mock-data shape.
+
+## Extraction Rules
+
+Turn the source material into implementation-ready WBS rows. Capture:
+
+- `WBS ID`: hierarchical task identifier like `1.2.3`.
+- `WBS Phase`: the top-level phase number or grouping.
+- `Level 1`: major workstream.
+- `Level 2`: sub-workstream or work package.
+- `Description`: concrete implementation task.
+- `Recommended Staffing`: one or more roles.
+- `Estimated Hours`: scoped effort estimate.
+- `Estimated Weeks`: derived from hours, typically `hours / 40` unless the user specifies another assumption.
+- `Security Estimated Hours`: separate security effort when governance, compliance, IAM, key management, or control validation is part of the task.
+
+Prefer concrete task language over vague workstream labels. For example, use `Develop Terraform modules for core landing zone components` rather than `Build infrastructure`.
+
+## Planning Guidance
+
+- Break work into major streams such as strategy, discovery, landing zone, platform scaffolding, environment provisioning, security, automation, validation, handoff, and documentation when the source supports them.
+- Keep tasks implementation-specific and commercially safe. A task should be estimateable and understandable in a proposal or delivery plan.
+- Treat security, governance, networking, logging, CI/CD, IaC, and handoff work as first-class tasks rather than afterthoughts.
+- When the source is early-stage, use labeled assumptions rather than false precision.
+- If the work appears better suited to Pod tiers, reflect that in staffing language and task grouping without overstating committed implementation scope.
+
+## Generator Script
+
+Use `scripts/create_wbs_workbook.py` when generating the workbook from structured JSON.
+
+Typical flow:
+
+```bash
+python scripts/create_wbs_workbook.py --input extracted-wbs-data.json --output cloud-infrastructure-wbs.xlsx
+```
+
+Use this JSON shape:
+
+```json
+{
+  "title": "Cloud Infrastructure Work Breakdown Structure",
+  "contact": "delivery.team@example.com",
+  "date": "2026-04-29",
+  "generated_by": "Sogeti Jump Start Team",
+  "validated_by": "ACE practice",
+  "project_start": "2026-05-04",
+  "roles": [],
+  "tasks": []
+}
+```
+
+## Quality Checklist
+
+Before returning the workbook, confirm:
+
+- The output is an `.xlsx` file.
+- It contains `WBS`, `Roles`, `Gantt Chart`, and `RFP Reference` sheets.
+- The WBS sheet has concrete task rows with staffing, hours, and week estimates.
+- The Gantt sheet opens cleanly and its formulas do not show Excel errors.
+- The workbook is sanitized and does not contain real customer names or confidential data unless the user explicitly wants that and has provided it.
+- The terminology matches cloud infrastructure and implementation planning rather than generic workshop language.

package/.jumpstart/skills/work-breakdown-builder/evals/evals.json

@@ -0,0 +1,44 @@
+{
+  "skill_name": "work-breakdown-builder",
+  "evals": [
+    {
+      "id": 0,
+      "prompt": "Create a cloud infrastructure WBS workbook from these workshop notes: client needs an Azure landing zone, hub-spoke networking, Terraform-based deployment, CI/CD with security scanning, centralized logging, and disaster recovery planning. Security wants IAM controls, key management, and policy guardrails. The workbook should include implementation tasks, roles, estimated hours, a gantt-style schedule, and an RFP reference tab.",
+      "expected_output": "An .xlsx workbook with WBS, Roles, Gantt Chart, and RFP Reference sheets modeled on a cloud infrastructure work breakdown structure.",
+      "files": [],
+      "expectations": [
+        "The outputs include an .xlsx workbook.",
+        "The workbook contains the sheets WBS, Roles, Gantt Chart, and RFP Reference.",
+        "The WBS sheet contains at least 8 populated task rows with the required headers and numeric estimated hours.",
+        "The WBS tasks include security-oriented work such as IAM, key management, policy guardrails, or security scanning.",
+        "The Gantt Chart sheet contains formulas for schedule dates or task duration rather than only hardcoded values."
+      ]
+    },
+    {
+      "id": 1,
+      "prompt": "I have a transcript from an infrastructure modernization scoping call. Build a WBS workbook for a cloud data platform rollout with Apache Spark, Airflow, monitoring, environment automation, secrets management, and validation handoff. Pull concrete tasks, staffing, estimated hours, and project schedule placeholders from the transcript.",
+      "expected_output": "A cloud implementation planning workbook with task-level decomposition, role recommendations, effort estimates, and gantt-oriented schedule rows.",
+      "files": [],
+      "expectations": [
+        "The outputs include an .xlsx workbook.",
+        "The workbook contains the sheets WBS, Roles, Gantt Chart, and RFP Reference.",
+        "The WBS sheet includes concrete data-platform tasks mentioning Apache Spark, Airflow, monitoring, or environment automation.",
+        "The workbook includes a Roles sheet with at least 3 populated role rows.",
+        "The WBS sheet contains numeric estimated hours and formula-based estimated weeks values."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "Turn these rough RFP bullets into an Excel work breakdown structure: multi-environment platform setup, reusable IaC modules, compliance logging, DR readiness, release automation, and security validation. We need something the Jump Start team can use to size and discuss the work with a follow-on AI Innovation Pod or engineering team.",
+      "expected_output": "A proposal-ready WBS workbook with concrete work packages, hours, staffing, and a reusable reference layout.",
+      "files": [],
+      "expectations": [
+        "The outputs include an .xlsx workbook.",
+        "The workbook contains the sheets WBS, Roles, Gantt Chart, and RFP Reference.",
+        "The WBS sheet includes IaC, compliance logging, DR, release automation, and security validation tasks.",
+        "The workbook includes staffing recommendations and numeric estimated hours for the WBS rows.",
+        "The workbook is proposal-ready in structure, with an RFP Reference sheet populated from the WBS or schedule data."
+      ]
+    }
+  ]
+}

package/.jumpstart/skills/work-breakdown-builder/references/mock-wbs-data.json

@@ -0,0 +1,258 @@
+{
+  "title": "Cloud Infrastructure Work Breakdown Structure",
+  "contact": "delivery.team@sogeti.example",
+  "date": "2026-04-29",
+  "generated_by": "Sogeti Jump Start Team",
+  "validated_by": "ACE practice",
+  "project_start": "2026-05-05",
+  "roles": [
+    {
+      "Role": "Cloud Architect",
+      "Grade": "D / E",
+      "Location": "US",
+      "Job Description": "Leads the target-state architecture for landing zone, networking, platform services, and resilience design."
+    },
+    {
+      "Role": "Cloud Engineer",
+      "Grade": "C",
+      "Location": "India",
+      "Job Description": "Implements infrastructure using IaC, automation, and cloud service configuration."
+    },
+    {
+      "Role": "DevOps Engineer",
+      "Grade": "C",
+      "Location": "India",
+      "Job Description": "Builds CI/CD, deployment automation, configuration management, and environment workflows."
+    },
+    {
+      "Role": "Security Architect",
+      "Grade": "D",
+      "Location": "US",
+      "Job Description": "Defines security controls, policy guardrails, identity patterns, and compliance requirements."
+    },
+    {
+      "Role": "Data Platform Architect",
+      "Grade": "D / E",
+      "Location": "US",
+      "Job Description": "Designs the data-platform topology, cluster strategy, and platform dependencies."
+    },
+    {
+      "Role": "Data Platform Engineer",
+      "Grade": "C",
+      "Location": "India",
+      "Job Description": "Implements and tunes data platform services, cluster deployment, and observability hooks."
+    },
+    {
+      "Role": "Site Reliability Engineer",
+      "Grade": "C",
+      "Location": "India",
+      "Job Description": "Implements monitoring, alerting, reliability controls, and production-readiness automation."
+    },
+    {
+      "Role": "FinOps Lead",
+      "Grade": "D",
+      "Location": "US",
+      "Job Description": "Defines cost allocation, tagging, budget controls, and operating guardrails for cloud spend."
+    }
+  ],
+  "tasks": [
+    {
+      "WBS ID": "0.1.1",
+      "Level 1": "Establish Delivery Strategy",
+      "Level 2": "DevSecOps Strategy",
+      "Description": "Define pipeline strategy and environment promotion model",
+      "Recommended Staffing": "Cloud Architect, DevOps Engineer",
+      "Estimated Hours": 16,
+      "Security Estimated Hours": 0
+    },
+    {
+      "WBS ID": "0.1.2",
+      "Level 1": "Establish Delivery Strategy",
+      "Level 2": "DevSecOps Strategy",
+      "Description": "Finalize CI/CD, artifact, and security-scanning toolchain decisions",
+      "Recommended Staffing": "Cloud Architect, DevOps Engineer",
+      "Estimated Hours": 20,
+      "Security Estimated Hours": 8
+    },
+    {
+      "WBS ID": "1.1.1",
+      "Level 1": "Cloud Landing Zone Setup",
+      "Level 2": "Discovery & Design",
+      "Description": "Conduct workshops for IAM, networking, security, governance, and subscription structure",
+      "Recommended Staffing": "Cloud Architect, Security Architect",
+      "Estimated Hours": 28,
+      "Security Estimated Hours": 32
+    },
+    {
+      "WBS ID": "1.1.2",
+      "Level 1": "Cloud Landing Zone Setup",
+      "Level 2": "Discovery & Design",
+      "Description": "Design core resource hierarchy, policy inheritance, and environment boundaries",
+      "Recommended Staffing": "Cloud Architect",
+      "Estimated Hours": 20,
+      "Security Estimated Hours": 0
+    },
+    {
+      "WBS ID": "1.2.1",
+      "Level 1": "Cloud Landing Zone Setup",
+      "Level 2": "Foundational Build (IaC)",
+      "Description": "Develop Terraform modules for landing zone core components",
+      "Recommended Staffing": "Cloud Engineer",
+      "Estimated Hours": 50,
+      "Security Estimated Hours": 0
+    },
+    {
+      "WBS ID": "1.2.2",
+      "Level 1": "Cloud Landing Zone Setup",
+      "Level 2": "Foundational Build (IaC)",
+      "Description": "Automate network infrastructure, logging, and connectivity scaffolding",
+      "Recommended Staffing": "Cloud Engineer, DevOps Engineer",
+      "Estimated Hours": 42,
+      "Security Estimated Hours": 6
+    },
+    {
+      "WBS ID": "1.3.1",
+      "Level 1": "Cloud Landing Zone Setup",
+      "Level 2": "Security & Governance Implementation",
+      "Description": "Implement policy-as-code guardrails, secrets management, and baseline controls",
+      "Recommended Staffing": "Security Architect, Cloud Engineer",
+      "Estimated Hours": 36,
+      "Security Estimated Hours": 40
+    },
+    {
+      "WBS ID": "1.4.1",
+      "Level 1": "Cloud Landing Zone Setup",
+      "Level 2": "Validation & Handover",
+      "Description": "Validate landing zone deployment and document operational handoff procedures",
+      "Recommended Staffing": "Cloud Architect, Cloud Engineer",
+      "Estimated Hours": 18,
+      "Security Estimated Hours": 8
+    },
+    {
+      "WBS ID": "2.1.1",
+      "Level 1": "Platform Services & Apache Cluster Deployment",
+      "Level 2": "Platform Scaffolding (IaC)",
+      "Description": "Create reusable service templates for application and data platform stacks",
+      "Recommended Staffing": "Cloud Engineer, DevOps Engineer",
+      "Estimated Hours": 36,
+      "Security Estimated Hours": 0
+    },
+    {
+      "WBS ID": "2.2.1",
+      "Level 1": "Platform Services & Apache Cluster Deployment",
+      "Level 2": "Apache Stack Deployment",
+      "Description": "Automate deployment of Apache Spark clusters with baseline monitoring",
+      "Recommended Staffing": "Data Platform Architect, Cloud Engineer, Data Platform Engineer",
+      "Estimated Hours": 90,
+      "Security Estimated Hours": 0
+    },
+    {
+      "WBS ID": "2.2.2",
+      "Level 1": "Platform Services & Apache Cluster Deployment",
+      "Level 2": "Apache Stack Deployment",
+      "Description": "Automate deployment of Airflow and shared scheduling services",
+      "Recommended Staffing": "Data Platform Architect, Cloud Engineer, Data Platform Engineer",
+      "Estimated Hours": 70,
+      "Security Estimated Hours": 0
+    },
+    {
+      "WBS ID": "2.3.1",
+      "Level 1": "Platform Services & Apache Cluster Deployment",
+      "Level 2": "Environment Provisioning",
+      "Description": "Configure CI/CD for development and test environments",
+      "Recommended Staffing": "DevOps Engineer",
+      "Estimated Hours": 18,
+      "Security Estimated Hours": 4
+    },
+    {
+      "WBS ID": "3.1.1",
+      "Level 1": "Infrastructure as Code (IaC) & Automation Framework",
+      "Level 2": "Toolchain & Repository Setup",
+      "Description": "Set up Git repositories, branching model, and code-quality checks",
+      "Recommended Staffing": "DevOps Engineer",
+      "Estimated Hours": 27,
+      "Security Estimated Hours": 4
+    },
+    {
+      "WBS ID": "3.2.1",
+      "Level 1": "Infrastructure as Code (IaC) & Automation Framework",
+      "Level 2": "Validation & Release Readiness",
+      "Description": "Create validation pipeline, release checklist, and rollback procedure",
+      "Recommended Staffing": "DevOps Engineer, Security Architect",
+      "Estimated Hours": 24,
+      "Security Estimated Hours": 12
+    },
+    {
+      "WBS ID": "4.1.1",
+      "Level 1": "Observability & Reliability Enablement",
+      "Level 2": "Monitoring Foundation",
+      "Description": "Implement centralized monitoring, logging dashboards, and baseline alerting patterns",
+      "Recommended Staffing": "Site Reliability Engineer, Cloud Engineer",
+      "Estimated Hours": 40,
+      "Security Estimated Hours": 4
+    },
+    {
+      "WBS ID": "4.1.2",
+      "Level 1": "Observability & Reliability Enablement",
+      "Level 2": "Operational Readiness",
+      "Description": "Define incident runbooks, SLO checkpoints, and operational ownership handoff",
+      "Recommended Staffing": "Site Reliability Engineer, Cloud Architect",
+      "Estimated Hours": 24,
+      "Security Estimated Hours": 0
+    },
+    {
+      "WBS ID": "5.1.1",
+      "Level 1": "Backup, DR & Resilience",
+      "Level 2": "Resilience Design",
+      "Description": "Design backup, recovery, and cross-region resilience strategy for core services",
+      "Recommended Staffing": "Cloud Architect, Security Architect",
+      "Estimated Hours": 28,
+      "Security Estimated Hours": 8
+    },
+    {
+      "WBS ID": "5.2.1",
+      "Level 1": "Backup, DR & Resilience",
+      "Level 2": "Recovery Implementation",
+      "Description": "Automate backup policies, restore validation, and DR environment bootstrap",
+      "Recommended Staffing": "Cloud Engineer, Site Reliability Engineer",
+      "Estimated Hours": 34,
+      "Security Estimated Hours": 4
+    },
+    {
+      "WBS ID": "6.1.1",
+      "Level 1": "Identity, Access & Secrets",
+      "Level 2": "Identity Foundation",
+      "Description": "Implement role model, privileged access pattern, and workload identity configuration",
+      "Recommended Staffing": "Security Architect, Cloud Engineer",
+      "Estimated Hours": 30,
+      "Security Estimated Hours": 36
+    },
+    {
+      "WBS ID": "6.1.2",
+      "Level 1": "Identity, Access & Secrets",
+      "Level 2": "Secrets & Key Management",
+      "Description": "Configure key vault, secret rotation workflow, and access-policy automation",
+      "Recommended Staffing": "Security Architect, Cloud Engineer",
+      "Estimated Hours": 22,
+      "Security Estimated Hours": 28
+    },
+    {
+      "WBS ID": "7.1.1",
+      "Level 1": "FinOps & Operating Model",
+      "Level 2": "Cost Governance",
+      "Description": "Define tagging standard, budget thresholds, and chargeback-ready reporting model",
+      "Recommended Staffing": "FinOps Lead, Cloud Architect",
+      "Estimated Hours": 20,
+      "Security Estimated Hours": 0
+    },
+    {
+      "WBS ID": "7.1.2",
+      "Level 1": "FinOps & Operating Model",
+      "Level 2": "Handoff & Enablement",
+      "Description": "Prepare operating model, knowledge transfer plan, and support transition checklist",
+      "Recommended Staffing": "Cloud Architect, FinOps Lead, Site Reliability Engineer",
+      "Estimated Hours": 24,
+      "Security Estimated Hours": 0
+    }
+  ]
+}

package/.jumpstart/skills/work-breakdown-builder/references/wbs-structure.md

@@ -0,0 +1,67 @@
+# Cloud Infrastructure WBS Structure
+
+Use this structure when the live example workbook is not available.
+
+## Sheets
+
+| Sheet | Purpose | Key Columns |
+| --- | --- | --- |
+| WBS | Primary task breakdown and effort estimate | WBS ID, WBS Phase, Level 1, Level 2, Description, Recommended Staffing, Estimated Hours, Estimated Weeks, Security Estimated Hours |
+| Roles | Reference sheet for staffing terminology | Role, Grade, Location, Job Description |
+| Gantt Chart | Time-phased task view derived from WBS tasks | Task, Role, Duration (Weeks), Start, End, timeline columns |
+| RFP Reference | Compact summary useful for scoping/proposal reference | Start, Duration (days), End, Est Weeks, Est Hours, Recommended Staffing |
+
+## Task Extraction Rules
+
+- Use hierarchical WBS IDs such as `1.1.1`, `1.1.2`, `2.3.1`.
+- `WBS Phase` can be derived from the first digit in `WBS ID` when needed.
+- `Level 1` should represent the major implementation domain, such as `Cloud Landing Zone Setup` or `Infrastructure as Code (IaC) & Automation Framework`.
+- `Level 2` should represent the sub-phase or work package, such as `Discovery & Design`, `Foundational Build (IaC)`, or `Validation & Handover`.
+- `Description` should be task-specific and estimateable.
+- `Recommended Staffing` should use roles from the Roles sheet where possible.
+- `Estimated Hours` should be numeric and reflect task-level effort.
+- `Estimated Weeks` should be formula-driven from hours unless the user provides a different staffing assumption.
+- `Security Estimated Hours` is optional and should be used for IAM, policy, secrets, compliance, logging-control, validation, or security-architecture work.
+
+## Suggested Workstreams
+
+- Delivery strategy and DevSecOps setup.
+- Cloud landing zone setup.
+- Infrastructure as Code and automation framework.
+- Platform services and data platform deployment.
+- Security and governance implementation.
+- DR / resilience / monitoring / handoff.
+
+## Mock Data Shape
+
+`mock-wbs-data.json` uses this structure:
+
+```json
+{
+  "title": "Cloud Infrastructure Work Breakdown Structure",
+  "contact": "delivery.team@example.com",
+  "date": "2026-04-29",
+  "generated_by": "Sogeti Jump Start Team",
+  "validated_by": "ACE practice",
+  "project_start": "2026-05-04",
+  "roles": [
+    {
+      "Role": "Cloud Architect",
+      "Grade": "D / E",
+      "Location": "US",
+      "Job Description": "..."
+    }
+  ],
+  "tasks": [
+    {
+      "WBS ID": "1.1.1",
+      "Level 1": "Cloud Landing Zone Setup",
+      "Level 2": "Discovery & Design",
+      "Description": "Conduct workshops for IAM, networking, security, governance",
+      "Recommended Staffing": "Cloud Architect, Security Architect",
+      "Estimated Hours": 28,
+      "Security Estimated Hours": 40
+    }
+  ]
+}
+```