Back to Guides

Command Dependency Matrix

Complete dependency map for all 24 G-Cloud Kit workflow commands (26 total including init and pages), showing what each command reads, writes, and requires.

Files Read by Each Command

R = Required (command will error without it) | o = Optional (reads if present, proceeds without)

Commandsupplier-profileservice-designsddpricingsecuritydeclarationsfia-skillscompliance-fwspend-dataurnsmergestender-inteltemplate
supplier-profilesupplier-profile-template
service-designRservice-design-template
sdd-lot1RRsdd-lot1-template
sdd-lot2RRsdd-lot2-template
sdd-lot3RRRsdd-lot3-template
pricingRopricing-template
securityRRosecurity-template
declarationRdeclaration-template
reviewRRRooo
compareRooo
tendersoRotenders-template
submission-packRRRRRR
storyRooooostory-template
salesRsales-analysis-template
marketplace-data
customerRR
targetsRRoo
marketingRRomarketing-template
customize
planooooooplan-template
healthoooooo
diagramoRo
dpiaRRRoRdpia-template
presentationRoRoopresentation-template

tender-intel = services/{NNN}-{name}/tender-intel.md, produced by /gcloud-kit:tenders. Every consumer reads it as a soft dependency — it enriches the output when present and is silently skipped when absent.

Files Written by Each Command

CommandOutput
supplier-profileservices/supplier/supplier-profile.md
service-designservices/{NNN}-{name}/service-design.md
sdd-lot1services/{name}/sdd.md
sdd-lot2services/{name}/sdd.md
sdd-lot3services/{name}/sdd.md
pricingservices/{name}/pricing.md
securityservices/{name}/security.md
declarationservices/supplier/declaration.md
reviewservices/{name}/review-report.md
compareservices/{name}/competitor-analysis.md
tendersservices/{name}/tender-intel.md
submission-packservices/{name}/submission/{checklist,guide,answers-export}.md
storySUBMISSION-STORY.md
sales.gcloud/market-analysis/sales-analysis.md
marketplace-data.gcloud/market-analysis/marketplace-stats.md, services/{name}/market-analysis/{competitors,keywords}.md
customerConsole output only
targetsConsole/file output
marketingservices/{name}/marketing/{press-release,social-media,blog-post,email-templates,content-calendar}.md
customize.gcloud/templates/{name}-template.md
planSUBMISSION-PLAN.md
healthConsole + docs/health.json
diagramservices/{name}/diagrams.md
dpiaservices/{name}/dpia.md
presentationPRESENTATION.md (portfolio) or services/{name}/presentation.md (per-service)

Command Dependency Chain

supplier-profile ──┬──→ service-design ──┬──→ sdd-lot1/2/3 ──┬──→ pricing
                   │                     │                    ├──→ security
                   │                     │                    ├──→ compare (optional SDD + tender-intel)
                   │                     │                    ├──→ tenders (optional SDD) ┄┄→ feeds pricing/compare/targets
                   │                     │                    ├──→ marketing (optional SDD)
                   │                     │                    ├──→ dpia (requires SDD + security optional)
                   │                     │                    └──→ presentation (requires SDD)
                   │                     │
                   │                     ├──→ diagram (requires design, optional SDD)
                   │                     │
                   ├──→ declaration       │
                   │                     │
                   └──→ story            └──→ review ──→ submission-pack
                        (scans all)          (reads all)   (requires all)

Scans existing (no hard requirements):
  plan ──────────── scans all artifacts, generates timeline
  health ────────── scans all artifacts, checks completeness

Independent (no project file dependencies):
  customize ─────── copies plugin templates to .gcloud/templates/
  sales ─────────── uses spend-data CSV only
  marketplace-data ─ uses external marketplace dataset
  customer ───────── uses URN + merge CSVs only
  targets ────────── uses URN + spend-data CSVs (optionally enriched by tender-intel)

Key Observations

  1. supplier-profile is the root dependency — 13 of 24 workflow commands read it.
  2. service-design is the second gate — all per-service commands require it.
  3. submission-pack is the strictest — it requires all 6 documents (profile, declaration, design, SDD, pricing, security).
  4. Six commands are fully independent (customize, sales, marketplace-data, customer, targets) or scan-only (plan, health) — they can run at any time.
  5. security reads the SDD but doesn't hard-fail without it (uses 2>/dev/null), making it optional.
  6. sdd-lot3 is the only SDD command that also reads reference data (sfia-skills.md).
  7. dpia is the most context-rich per-service command — reads 4 artifacts plus compliance-frameworks.md reference.
  8. presentation works at both portfolio and per-service level.
  9. All commands now consistently use services/supplier/supplier-profile.md for the supplier profile path.
  10. tenders is a producer whose tender-intel.md artefact is a soft input to pricing (awarded-value price anchor), compare (real competitor award evidence), and targets (live award-active buyers) — each degrades gracefully when it is absent.