Skip to content

Agent Operating Guide

/coach-starter-pack

Apply the canonical 7-item starter pack, optionally overlaid with audit, SOX, regulatory, or GRC seed data, as a bulk-import JSON the admin pastes into the Bulk Import page.

The fastest path to a usable schema for a new tenant. The skill applies the canonical shared starter pack, seven item types: audit, issue, risk, control, process, policy, and authority_source, optionally overlaid with domain seed data for one of audit, sox, reg, grc, or a generic catch-all. It produces a bulk-import JSON you paste at the admin Bulk Import page (/en/admin/bulk-import); it never writes to the tenant directly and never routes through suggest_change. Re-running is idempotent: it diffs against your current schema and emits only the delta.

When you’re bootstrapping a brand-new tenant for a standard domain and want a working schema in minutes instead of designing one. If your work doesn’t fit audit, SOX, regulatory, or GRC, or you need custom types and relationships, design it interactively with /coach-schema-design instead.

Flag Required Notes
<kind> No Positional: one of audit, sox, reg, grc, generic. If omitted, the skill asks which pack matches your work.
--core-only No Apply only the shared 7-item core, with no domain overlay.
--from <path> No Use a custom JSON as the overlay instead of a canned pack (still on top of the shared core).
--dry-run No Print the proposed item types and fields without writing the output file.

/coach-starter-pack sox loads the shared 7-item core, overlays the SOX seed authority_source items (SOX §404 / §302 / §906 and PCAOB AS 2201), validates the merged pack, then diffs it against your current schema so types that already exist are skipped. It writes .coworkcanvas/starter-packs/sox-<date>.json for you to paste at /en/admin/bulk-import.

  • Idempotent at the item-type level: re-running skips types that already exist (warning “audit already exists; skipping”) and surfaces any new fields on existing types for your confirmation. Safe to run more than once.
  • Framework mapping (SOC 2 TSC, ISO Annex A, SOX 404) is done by linking to authority_source items via the cites_authority_sources field: there’s no separate compliance-criteria list.
  • The sox, grc, and reg overlays are seed-only (they add sample authority_source items and declare no new types); the audit overlay additionally adds the audit-planning types audit_universe_entity and audit_plan used by the risk-scoring and annual-planning workflows.
  • It validates twice as a hard gate, the merged pack, then the written file, because filtering out existing types can leave a dangling RELATION target, and the on-disk file is what you actually paste.