// readme

tribe-common

Common classes and functions used in our plugins

Specs and planning

Work on this repository is planned before it is written, using OpenSpec. This is enforced — every pull request is checked for a plan.

Plans do not live here. A TEC feature routinely spans several repositories, so a spec kept in one of them is invisible from the others. They all live in one shared store instead: the-events-calendar/plans.

First time only

npm install -g @fission-ai/openspec
git clone git@github.com:the-events-calendar/plans.git ~/repos/tec-plans
openspec store register ~/repos/tec-plans --id tec-plans
openspec config set defaultStore tec-plans

The clone path is yours to choose. The --id is not — every command refers to the store as tec-plans.

Working on a ticket

  1. Create the change before writing code, named after the ticket in lower case. OpenSpec requires kebab-case and rejects anything else, so the ticket SOFT-1234 becomes the change soft-1234: openspec new change soft-1234 --store tec-plans --description "what this does"
  2. Write…