Terreno Planning

Plugin terreno-planning in TerrenoLabs/terreno. Commands read from the repo's manifest — today.

Skills (35)

• ai-prompt-governance

  Invoke when adding, modifying, or reviewing any prompt used by `@terreno/ai` (AIService methods, system prompts, helpers) or when shipping a new AI product feature (dataset, evaluators, experiments, production label, live feedback). Provides prompt-as-constant/registry rules, SOP loop, temperature p

• attach-pr-media

  Upload screenshots or videos from a local path to GitHub and embed them in a pull request comment or body, using only the gh CLI token (no browser). Use after verify-ui-changes captures evidence, or when asked to "attach screenshots to the PR", "upload images to GitHub", or "put the recording on the

• backend-test-env

  Invoke when writing tests that mutate `process.env` in `@terreno/api`, `@terreno/ai`, or `example-backend` — feature flags, auth secrets, integration toggles. Covers the preload contract, `setupEnvironment()`, and safe mutation patterns. Lifecycle composition: Pick when writing these tests; Roast wh

• backfill-regression

  Backfill a repository's manual regression suites. Survey the app for behavior that only a developer or QA can check by hand (push notifications and other hardware or OS behavior, real email or SMS delivery, full cross-device flows, how the app feels) plus a short check that the app works as intended

• backfill-user-guide

  Backfill a repository's end-user guide. Survey the shipped app for user-facing features (screens, navigation, forms, settings, admin tools) that have no guide page, draft pages in the user-guide format one area at a time, and have the human approve, edit, or deny each set before anything is written.

• bootstrap-mcp-server

  Bootstrap a backend-only Terreno MCP server that ships as a single Bun executable with the admin console embedded. Scaffolds the backend with create-terreno-app, drops the frontend, registers MCP tools, service tokens, optional MCP OAuth using the admin console's consent screen, a request log, tool

• building-admin-interfaces

  Build Terreno admin UIs with @terreno/admin-frontend and @terreno/admin-backend. Use when adding or changing admin screens, AdminShell sidebar nav, AdminHome, custom screens, AdminScreenRouter, AdminProvider widgets, admin-spa routes, or operator tools. Covers where models vs custom screens vs platf

• building-terreno-apps

  Complete guide for building Terreno full-stack Expo apps with @terreno/ui, Expo Router, and @terreno/syncdb. Covers layout, forms, navigation, theming, screen patterns, and when to use Expo Go vs custom builds.

• debug-syncdb-with-mcp

  Invoke when debugging SyncDB local state, stale data, outbox stalls, conflicts, cursor/stream drift, reconciliation, or offline behavior in a running Terreno app. Uses terreno-mcp-local to inspect, snapshot, compare, mutate, flush, merge, and repair SyncDB state. For general Terreno debugging (logs,

• debug-with-mcp

  Standard way to debug and drive Terreno apps: use terreno-mcp-local (and hosted terreno for docs) instead of guessing from code or pasted logs. Invoke for any bug, 500/403, wrong data, crashes, empty screens, sync/offline issues, auth/storage problems, or verifying a fix on web or native. Use debug-

• deploy-gcp

  Deploy a Terreno app to GCP — Cloud Run backend and GCS+CDN static web. Trigger phrases include "deploy to GCP", "deploy to Cloud Run", and "ship the backend".

• generate-release-announcements

  Generate, validate, and optionally upload a multi-announcement Markdown release pack for @terreno/announcements. Use when asked to announce a product release, turn release notes or a Linear Release into in-app announcements, create an announcement pack, or upload release announcements as drafts or l

• generate-sdk

  Regenerate the example-frontend SDKs from the example-backend's OpenAPI spec with terreno-syncdb-codegen: store/apiSdk.ts (typed request hooks for every non-synced route, `bun run sdk`) and store/syncDbSdk.ts (synced collection hooks, `bun run sync-sdk`). Handles dependency install, backend startup,

• mongoose-schema-safety

  Invoke when making any Mongoose schema change: adding/removing/renaming fields, creating a new model, adding indexes, or writing a backfill migration. Provides the five-type pattern, risk matrix, type file checklist, and rollout safety steps for Terreno backends.

• set-up-social-login

  Set up Google, GitHub, and Sign in with Apple in a Terreno app on Better Auth: server config, callback URLs for local dev, previews, and the stable deploy, provider registration, secrets, trying the providers on one preview first, choosing same-site hosts, and checking the result. Use when asked to

• store-assets

  Produce App Store and Google Play listing assets for an Expo app: store-sized screenshots (6.5-inch iPhone, 13-inch iPad, 1080x1920 Android phone) captured by Maestro flows that log in with test accounts, the Play feature graphic (1024x500 banner), and the Play high-res icon (512x512). Also keeps a

• terreno-1-grow

  Research, clarify, shape, and approve an implementation-ready IP and task list. Use whenever the user asks to plan, shape, spec, or scope substantial work ("help me plan X", "how should we build Y") or to revise an existing plan; not for implementation or PR operations.

• terreno-2-pick

  Implement one approved IP/task slice with behavior-focused TDD, then roast it and pick the next unblocked task until the approved list is done. Not for planning, skipping Roast, or PR submission.

• terreno-3-roast

  Independently prove or disprove the current task against its IP criteria, then return. Do not pick or start the next task. Pick owns the inner loop. Use after Pick, preferably in a fresh context; not for fixing implementation code.

• terreno-4-brew

  Move a Roast-verified implementation into GitHub review: final checks, branch hygiene, commit/push, PR setup, evidence attachment, confirm product CI on every discovered host (GitHub Actions, CircleCI, Buildkite, and similar), and wait in-process for async review bots (Bugbot, CodeQL) before exit.

• terreno-5-taste

  Perform one reactive iteration against the PR's current head. Wait through provider CLI hooks until async review bots and product CI finish (GitHub CLI or CircleCI CLI in a watch loop), inspect every discovered host, mergeability, and reviews, act on what is actionable. Record failed tests from the

• terreno-backend-api

  Guidelines for creating backend APIs with @terreno/api on Express/Mongoose. Covers when to use Terreno backend vs Expo API routes, modelRouter CRUD, permissions, modelRouter actions (not app.get/app.post), OpenAPI generation, and the SDK codegen pipeline. Use when adding models, routes, auth, or ser

• terreno-backend-tests

  Write and fix Bun tests for a Terreno backend: modelRouter routes and actions, permissions, Mongoose models and hooks, services that call SendGrid / Twilio / Expo push / Cloud Tasks / GCS / AI models, env-dependent code, time, and async side effects. Covers supertest + @terreno/test helpers, auth to

• terreno-data-fetching

  Use when implementing or debugging ANY network request, API call, or data fetching in a Terreno app. Covers syncdb collection CRUD, generated request hooks (store/apiSdk.ts) for non-synced routes, session auth, socket pushes, feature flags, admin's host-bound fetch client, and SDK regeneration. Repl

• terreno-frontend-tests

  Write and fix frontend tests for a Terreno Expo app: Bun + React Native Testing Library unit tests for components, screens, hooks, Redux/RTK and syncdb data, and Playwright web E2E for flows across screens and the backend. Covers renderWithTerreno, testID selectors, mocking data hooks without leakin

• terreno-mobile-tests

  Write and fix mobile tests for a Terreno Expo app on iOS and Android: Maestro flows that drive the native app on a simulator or emulator, and Bun unit tests for Platform.OS-specific code. Covers testID selectors on native, login subflows, waiting, platform branches, keyboards and system dialogs, rea

• terreno-pick-roast-loop

  Drive an approved plan through every Pick–Roast cycle until all tasks pass or a genuine human decision is required. Continue through recoverable engineering failures, keep a complete run ledger, and when input is required present the overall state, completed work and evidence, options, recommendatio

• terreno-planning-loop

  Drive the planning plugin from the current task list, optionally restricting which stages run (Grow, Pick, Roast, Brew, Taste). Not a sixth stage — an outer loop that invokes existing stage skills. Use when asked to run the planning loop, walk the task list, or restrict work to selected phases.

• terreno-prd

  Interview the app owner and write a full product requirements document (problem, why now, solution, user stories, measurable success metrics, constraints, rollout, out of scope), then publish it where the repository tracks work. Sized for one owner and one or two developers. Runs ahead of Grow; expl

• terreno-taste-sweep

  Outer loop over open PRs you authored that currently have a merge conflict, a failing product-CI job on any discovered host (GitHub Actions, CircleCI, Buildkite, and similar), or an unanswered review-bot thread. Isolates each PR and reinvokes Taste until mergeable or blocked. Skip drafts and already

• terreno-test-setup

  Bootstrap or repair the test setup of a Terreno app: backend Bun tests with in-memory Mongo, frontend Bun + React Native Testing Library unit tests and Playwright web E2E, and mobile Maestro flows on iOS/Android. Use when an app has no tests yet, `bun test` finds nothing or crashes on import, a new

• terreno-ui

  Build UI with @terreno/ui — Terreno's React Native component library with a large component set and a three-layer theming system. Use when adding or reviewing layout, forms, tables, modals, feedback, or navigation chrome. Covers component selection, Box/Page patterns, theme props, and when NOT to us

• update-docs

  Keep Terreno docs in sync whenever behavior, public API, architecture, or operator workflow changes. Read architecture docs first; write Diátaxis pages in the same slice; regenerate generated docs. Lifecycle composition: Pick when behavior and docs change together; Roast proves docs; Brew is the fin

• upgrading-terreno

  Upgrade Terreno lockstep @terreno/* packages. Trigger with "upgrade Terreno", "bump @terreno packages", "update to the latest Terreno", or "upgrade terreno version".

• verify-ui-changes

  Mandatory when any feature touches the frontend. Bring up a stack you own, log in, drive the change under the required checks (right page, not blank, no error overlay, console clean, DOM assertion, interaction proof, screenshot), run the repository's Maestro flows on the simulator for mobile-focused

Subagents (2)

• pre-commit

  Run lint, type check, and related tests on the current working tree. Fix any failures encountered. Use before commits and after CI fix attempts.

• ui-verifier

  Verify UI changes end to end when the parent briefing lists UI files. Compile, lint, UI tests, bring up a stack you own, log in, exercise the named feature under the required checks, run the matching Maestro flow (or direct simulator commands when the app has no Maestro) for mobile-focused work, rep

Similar plugins