Command catalog for humans building the split-payments product.

Slacker-style commands for reading docs, integrating games, connecting marketplaces, designing split rules and checking deploys. If we later build a real Slack app, these commands become the first slash-command map.

Test game.integrate Test marketplace.integrate Test split.design Slack API docs

partner.plan

Plan a future partner integration.

Goal

Turn a partner use case into a scoped implementation plan.

Read First

  • SPLIT_PAYMENTS_PRODUCT.md
  • FUNCTION_CATALOG.md

Steps

  • Choose use case.
  • Choose custodial split first.
  • Define destinations.
  • Define webhooks.
  • Map missing functions.

Acceptance Checks

  • Flow has payment source, split rule, destination and status model.

CLI

php spark product:slacker partner.plan

Slack Or Slacker?

The current implementation is Slacker-style: a human command catalog and Spark CLI command. Slack's own platform provides Web API, Events API, Status API and app tooling. If we want this inside Slack later, these commands can become slash commands or Slack app actions.

Open Slack API docs Open command JSON