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

docs.read

Read the product docs in the right order.

Goal

Give a human or AI-agent the shortest safe path through the documentation.

Read First

  • WELCOME_REPLACEMENT.md
  • SPLIT_PAYMENTS_PRODUCT.md
  • FUNCTION_CATALOG.md
  • API.md

Steps

  • Start with product context.
  • Use the function catalog as the map.
  • Use API.md only when implementing endpoint calls.

Acceptance Checks

  • You can explain game, marketplace and generic split flows.

CLI

php spark product:slacker docs.read

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