demoverse: Skill for Claude Code

/pipeline-update

The heartbeat of the demo world. One increment = one week of a real B2B SaaS pipeline: a couple of deals open, the open ones each take one step forward, the ones that have run their cycle close, and every one of those events leaves the one or two touch points a real team would have left behind.

This is not /backfill-opps. That one takes a deal that already exists and generates its entire sales cycle at once. That is the historical seed motion. This one adds a thin slice of new life to many deals. Never generate a full detail layer for a deal here. A deal born this week has had exactly one discovery call, and maybe an intro email. Its Evaluation call has not happened yet. It happens in a later increment, when the deal reaches Evaluation.

Steps

1. Advance. npm run pipeline (one week). For a longer jump or a heavier intake: npm run apply -- --weeks=N --new-opps=M.

   The engine echoes the active Tier-2 directives, the resolved increment, and any --new-opps override before writing anything. Read that back and confirm it is what was asked for. It then prints touch points planted this increment, grouped by deal:

   opp-291  Acme Corp (Discovery/open)      art-xxx:call_transcript art-xxy:email_exchange
   opp-285  Veltrix (Negotiation/open)      art-xxz:call_transcript
   opp-278  Orchard Ledger (Closed/lost)    art-xya:survey art-xyb:ae_note
   

   That grouping is the work list. A forced increment steps simNow past the real calendar. The engine warns how far ahead the world will sit. If it is already several periods ahead, say so and let the operator decide before continuing.

2. Fill: one opp-filler subagent per deal, in parallel. An increment is small (a handful of artifacts spread over several deals), so launch the whole wave at once: one subagent per opp- line above, plus one for any unattached artifacts (competitive_q). Give each the request dir (state/requests/<periodIndex>/) and only its artifact ids.