refactored: to utilise the google adk and production grade agent

app/skills/packaging_guide/SKILL.md

@@ -1,20 +1,37 @@
 ---
 name: packaging_guide
 phase: package
-description: Guidance for assembling the comprehensive solution-architecture-guide.md.
+description: Guidance for assembling the comprehensive solution-architecture-guide.md following Google's official 8-section output template.
 ---
 
 # Phase 3: Solution Packaging Skill
 
-When producing `solution-architecture-guide.md`:
+When producing `solution-architecture-guide.md`, follow Google's official 8-section solution architecture output template:
 
-1. **Consolidate Artifacts**: Combine key insights from `docs/requirements.md`, `docs/architecture.md`, `architecture.mmd`, `terraform/`, and `validation-results.md`.
-2. **Guide Structure**:
-   - Executive Overview & Problem Statement.
-   - Selected GCP Product Architecture & Rationale.
-   - Embedded Mermaid Architecture Diagram.
-   - Terraform Infrastructure Blueprint & Deployment Instructions.
-   - Pre-deployment Validation Evidence & Compliance Matrix.
-   - Operations, Monitoring, and Maintenance Runbook.
-3. **Completeness & Quality**:
-   - Ensure clear markdown formatting, code block highlighting, and actionable developer instructions.
+1. **Executive summary and workload overview**
+   - High-level business goals, workload description, and proposed solution architecture summary.
+2. **Requirements and current state**
+   - **2.1. Functional requirements**: Business processes, key activities, and use cases.
+   - **2.2. Non-functional requirements**: Security, reliability, cost, operations, performance, and sustainability requirements.
+   - **2.3. Current state**: Existing As-Is architecture, pain points, and migration drivers.
+   - **2.4. Dependencies**: Internal and external system dependencies.
+3. **Technical decomposition of the workload**
+   - Layered breakdown of application tiers and logical components.
+4. **Proposed solution architecture**
+   - **4.1. Google Cloud products and features mapping**: Selected products mapping table with justifications, doc citations, and alternatives considered.
+   - **4.2. Architecture diagram**: Embedded Mermaid diagrams for As-Is (Before) and Target Google Cloud (After) architecture.
+   - **4.3. Architecture description**: Data flow and task/control flow between components.
+5. **Design and configuration recommendations** (Architecture Framework Pillars)
+   - 5.1 Security, privacy, and compliance (IAM, encryption, network security)
+   - 5.2 Reliability (Redundancy, disaster recovery, RTO/RPO)
+   - 5.3 Operational excellence (Monitoring, logging, IaC)
+   - 5.4 Cost optimization (Sizing, autoscaling, pricing models)
+   - 5.5 Performance efficiency (Caching, database & query optimization)
+   - 5.6 Sustainability (Resource efficiency, serverless adoption)
+6. **Deployment guidance**
+   - **6.1. Deployment prerequisites**: Required GCP APIs, SDK tools, and permissions.
+   - **6.2. Step-by-step deployment instructions**: Complete Terraform IaC blueprint (`terraform/main.tf`) and CLI execution runbook.
+7. **Validation plan**
+   - Pre-deployment validation results, dry-run checks, and Verification Checklist.
+8. **References**
+   - Citations and documentation links grounded by Google Developer Knowledge MCP.

app/skills/source_discovery/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: source_discovery
+phase: source_discover
+description: Guidance for discovering, auditing, and documenting the existing pre-emptive source environment before target migration.
+---
+
+# Phase 0a: Existing Source Environment Discovery Skill
+
+When auditing and discovering an existing pre-emptive source environment:
+
+1. **Assess As-Is Architecture**: Analyze existing workloads, on-premises applications, legacy infrastructure, or existing cloud provider setups.
+2. **Identify Existing Components**:
+   - Monolithic / legacy application services & ingress endpoints.
+   - Self-hosted database engines (e.g. MySQL, PostgreSQL, Oracle) or legacy file shares.
+   - Traditional messaging queues (e.g. RabbitMQ, ActiveMQ).
+   - Network topology, firewall rules, and authentication mechanisms.
+3. **Capture Source Metrics & Pain Points**:
+   - Current scale, capacity constraints, downtime risks, and operational bottlenecks.
+   - Security vulnerabilities, compliance gaps, and maintenance costs.
+4. **Document Source Architecture**:
+   - Produce a clear `docs/source-architecture.md` baseline documenting the "Before" state.
+   - Render a Mermaid diagram representing the existing source topology (`source-architecture.mmd`).