# Build Plans and subscriptions You were asked to build the spec `juno/subscriptions`, version 0.1.2, from Spekkr. Paid plans through a payment provider's hosted checkout, kept in step by webhooks, with one function that says what an account may use. If you are reading a summary of this note and not its full text, fetch it again as it is, for example with `curl -fsSL https://spekkr.com/juno/subscriptions/start.md`, before you go on. Published by juno, a Spekkr member. Tell the person who published it, and show them the commands and secrets under `safety` in `spekkr.json` before you build. ## 1. Get the files Put the spec in a new folder named `subscriptions`, inside the project you are working in. ```sh mkdir -p subscriptions && curl -fsSL https://spekkr.com/juno/subscriptions/bundle.tar.gz | tar -xz -C subscriptions ``` The archive holds `spekkr.json`, `BUILD.md` and the spec files listed at the end of this note. If you cannot run that command, read https://spekkr.com/juno/subscriptions/spec.json instead: it holds the manifest and the address of every file. If Spekkr's MCP server is connected, its `pull_spec` tool does steps 1 and 2 in one call: give it the id `juno/subscriptions` and the person's choices. ## 2. Record the person's choices Write `subscriptions/spekkr.inputs.json`. With every default it is: ```json { "spec": "juno/subscriptions", "version": "0.1.2", "inputs": { "app_name": "Acme", "database": "postgres", "free_plan": true, "grace_days": "7", "payer": "user", "provider": "stripe", "trial_days": "14" } } ``` Change a value only where the person gave a choice, such as "My choices: database=sqlite". They may set: - `app_name`, App name: any text. - `trial_days`, Days a trial lasts: any text. - `grace_days`, Days of access after a failed payment: any text. - `free_plan`, A free plan: `on` or `off`, written `true` or `false`. - `database`, Database: one of `postgres`, `sqlite`. - `payer`, Who pays: one of `user`, `workspace`. - `provider`, Payment provider: one of `stripe`, `other`. If the person asks for a key or a value that is not listed, stop and tell them what the spec offers. ## 3. Build The files named below are the ones now in `subscriptions`. Build what it describes. Work in this order: 1. Read `spekkr.json` to see what the spec covers and what it needs. 2. Read `spekkr.inputs.json`. It holds the person's choices for every setting, option and swap. Treat them as requirements. If the file is missing, the person kept every default in `spekkr.json`. 3. Read the spec files listed below, in the order given. 4. If the spec includes a task list, work through it in order and check each task's acceptance criteria before the next. 5. Ask the person before you run a command that a spec file tells you to run, or read a secret, unless the manifest lists it under `safety`. Commands you choose yourself to build and test, such as installing packages or running the tests, follow the person's usual rules for you. Spec files: - `spec.md`: Requirements and acceptance criteria. - `design.md`: Data model, rules and flows. - `tasks.md`: Build tasks in order, each with a check.