Back to Guides

/gcloud-kit:plan

Generate a G-Cloud submission plan with timeline, Mermaid visualisations, and phase checklists.

Overview

Creates a structured submission plan that maps out the full journey from initial setup to marketplace launch. Scans existing artifacts to pre-populate progress, calculates timeline estimates based on service count and target date, and produces Mermaid Gantt charts and workflow diagrams for stakeholder communication. Re-run at any stage to update the plan with latest progress.

Usage

/gcloud-kit:plan
/gcloud-kit:plan 3 Lot 2 services, target April 30
/gcloud-kit:plan Update progress

Arguments: Optional — service count, target date, lot numbers. If not provided, the command asks interactively.

Prerequisites

  • None — works at any stage, even before /gcloud-kit:init
  • Existing artifacts are automatically detected and marked as complete

Output

SUBMISSION-PLAN.md (project root)

Template used: plan-template.md

What it does

  1. Gathers planning inputs (service count, target date, lots) via interactive prompt or arguments
  2. Scans services/ for existing artifacts — supplier profile, declarations, service designs, SDDs, pricing, security, reviews, submission packs, marketing content
  3. Reads the plan template
  4. Calculates phase durations based on service count (1 service ~ 6-9 days, 3 services ~ 11-15 days, 5 services ~ 17-23 days)
  5. Generates a Mermaid Gantt chart with calculated dates and progress status
  6. Generates a Mermaid workflow flowchart showing the command dependency chain
  7. Builds 6 phase checklists with completion status:
    • Phase 1: Foundation (supplier-profile, declaration)
    • Phase 2: Service Design (service-design per service)
    • Phase 3: Service Definition (sdd-lot1/2/3 per service)
    • Phase 4: Supporting Documents (pricing, security per service)
    • Phase 5: Review & Submit (review, submission-pack per service)
    • Phase 6: Go-to-Market (marketing, story, pages)
  8. Identifies the critical path and bottlenecks
  9. Creates a risk register with common submission risks
  10. Documents resource requirements and external dependencies
  11. Writes the plan and shows a concise progress summary

Related commands