Skip to content

v0.14.0 — /campaign: start a campaign with one command

Choose a tag to compare

@a-lottes a-lottes released this 12 Oct 13:44
· 135 commits to main since this release

One loop ships here: campaign-start, released through PR #72. Campaigns stay experimental.

Added

  • A new optional command, /campaign <name> [kind], starts a campaign for you. You no longer name the plugin folder or build the file by hand: it reads the available kinds and the template itself, asks only what the chosen kind leaves open, and writes one draft at .spark/campaigns/<name>/campaign.md.
  • It stops at the draft. The draft is marked draft, the approval and the veto record stay blank, nothing is committed, and the closing message lists what is still unfilled and which session to run next. Approving and running a campaign remain your steps.
  • It is instructed to refuse, writing nothing, when the goal is not measurable, when you give several goals, when no kind fits, when the name is invalid or already taken, or when a kind is missing a required key.

Changed

  • The README and the campaigns guide now present /campaign as the way to start one; hand-starting still works, and running a campaign is still done by hand.
  • The docs now count eleven commands in total; the loop itself still has ten ceremonies.

Fixed

  • Nothing fixed; this release only adds. Limits to know: these checks are prompt material, so they make the behavior likely, never certain. In testing, a kind with a missing key was caught in 24 of 24 sessions but only after a fix (1 of 5 before it). A goal that is not measurable was refused 5 of 5, several goals 5 of 5, a taken name 5 of 5. Known small gaps, accepted: some drafts keep the placeholder title (5 of 16), the note about other running campaigns was missed once in 7, and the closing sentence is sometimes worded differently (4 of 5 verbatim). No campaign has run on a real project yet, and its real-world effectiveness is unmeasured.