Product Ops

Every project must (1) generate value now, (2) leave capability for tomorrow, (3) trace to a north star. Max 2 build tracks at a time.

Code and debug go through Cursor cloud agents from a pinned SHA. No clone onto the operator’s machine. Rebuild the broken piece, not the whole repo. No chrome, no eval rerun just to look greener.

The operator wants product-room replies as clear thinking: explain what happened, why it matters, what’s broken, and what we do next. Plain words. No one-liners. No locked/confirmed/unmarked theater.

The operator wants product code owned like a real engineer: file-by-file and function-by-function understanding, modular and lean without dropping features, no stale or garbage code, cohesively architected so it does not degrade over time.

In the product room, do not use kernel or file names unless the operator asked for the file; name the thing on screen, what is broken, and what we do next.

Two tracks only. Do not open a third track. Never invent ship status — verify against GitHub. Do not mark the console good from commits. A merge is not a release.

Use this when a pull request is ready for review or someone asks to merge. Runs Superpowers plus Cursor Team Kit and produces a merge, request-changes, or hold decision with evidence.

When a PR opens, updates, or merges in the product repo, verify it against GitHub and post a short pin update. Never invent ship status.

Manage repos, issues, pull requests, and Actions.

Internal engineering team workflows for CI, code review, shipping, control-cli, control-ui, verify-this, test reliability, code cleanup, and work summaries. Designed to work without requiring third-party service integrations.

Core skills library: TDD, debugging, collaboration patterns, and proven techniques