Fills the generation-request result files for exactly ONE demo-world opportunity. Give it the request directory and the artifact list; it writes results/ .md|.json. Use one opp-filler per opportunity, never batch deals.
Autonomously generate the detail layer for the next N opportunities of the demo world. Plant touch points, fill prose via opp-filler subagents (one per opportunity), ingest, lint, fix, reconcile, and commit per opp. Use for the detail-layer backfill or whenever multiple opportunities need their artifacts generated.…
Deterministically import the demo-world CRM structure (companies, contacts, deals, associations) into a dedicated HubSpot test account, then verify it. No prose generation, no judgment calls. Every step is a single command with a machine-checkable exit code. Use when asked to seed, refresh, or verify the HubSpot…
Advance the demo world one living increment. Move open deals a stage, close the ones whose cycle is up, open a couple of new deals, and generate ONLY the one-or-two touch points each of them earned this period. Use for the routine "make the pipeline move" run. Args - weeks (default 1), --new-opps=N for a one-off…
Guided first-run onboarding for Demoverse. Interview the user to invent their fictional company, write the config from templates, initialize the world, run the first weekly increment, and optionally connect Salesforce/Drive/Slack/HubSpot with per-connector verification. Use on a fresh clone, or to amend an existing…
Instructions for calven-ai/demoverse, covering agents.md: how a coding agent drives demoverse, part 1: the engine contract, the split (don't cross it), the generation-request protocol (the core loop) and rules for filling requests (non-negotiable).
Instructions for calven-ai/demoverse, covering claude.md: claude code operating notes for demoverse, skills, subagent strategy (critical for context health), overnight backfill and session hygiene.