/gcloud-kit:story
Generate a comprehensive submission story with timeline, achievements, and lessons learned.
Overview
Scans all project artifacts, extracts timeline data from git history or file modification dates, and produces a narrative document covering the entire submission journey. Includes executive summary, timeline visualisations, service portfolio summary, compliance status, and lessons learned.
Usage
/gcloud-kit:story
/gcloud-kit:story Focus on lessons learned
Arguments: Optional focus area.
Prerequisites
- Supplier profile must exist (
services/supplier/supplier-profile.md) - Service artifacts recommended for a complete story
Output
SUBMISSION-STORY.md (project root, 500–1000 lines)
Template used: .gcloud/templates/story-template.md
What it does
- Checks prerequisites (supplier profile must exist)
- Performs a comprehensive artifact scan — finds all
.mdfiles in the project - Extracts timeline from git history or file modification dates
- Analyses each artifact for key information
- Builds a submission summary (supplier overview, services listed, compliance status, market positioning)
- Generates 3 types of timeline visualisations:
- Gantt chart
- Command flow diagram
- Timeline table
- Calculates metrics (duration, service count, document count, certifications)
- Extracts lessons learned (what went well, improvements, recommendations)
- Writes the story document
Related commands
- /gcloud-kit:submission-pack — create submission bundle before documenting the story
- /gcloud-kit:review — review results feed into lessons learned