A senior ServiceNow architect suite: expert knowledge across enterprise architecture (CMDB, CSDM, APM, Service Mapping, Technical Debt), platform governance, delivery and requirements/scope management, and hands-on development (Fluent SDK .now.ts, GlideRecord scripting, now-sdk CLI/setup). Use when designing, reviewing, building, governing, or planning anything on the ServiceNow platform - from "where should this CI live in the CMDB?" to "write this Business Rule" to "how do we control scope creep?". Routes each task to the right sub-skill. Trigger on: ServiceNow, CMDB, CSDM, APM, Business Application, Application Service, Service Mapping, TPM/TRM, governance, update set, upgrade, user story, acceptance criteria, scope checkpoint, Fluent SDK, .now.ts, GlideRecord, Script Include, Business Rule, Client Script, now-sdk. Prefer a dedicated client- or project-specific skill when one exists; this suite is for generic ServiceNow work.
Senior ServiceNow Enterprise Architecture / CMDB / CSDM / APM knowledge for modeling the platform correctly. Use when classifying CIs, deciding table/class placement, designing CMDB or CSDM structure, modeling Business Applications vs Application Services (Service Instances) vs infrastructure CIs, planning Service Mapping, assessing Technical Debt via TPM/TRM, migrating legacy application records, or reviewing a dependency/relationship map. Trigger on: CMDB, CSDM, APM, EA Workspace, Business Application, Application Service, Service Instance, Configuration Item, cmdb_ci_business_app, cmdb_ci_service_discovered, svc_ci_assoc, Service Mapping, entry point, TPM, TRM, Technical Debt, class audit, CI classification, taxonomy, metamodel. Use even when the words "CSDM" or "APM" are not named but the task is clearly about where a thing lives in the CMDB or how applications map to infrastructure.
Generates GlideRecord queries, Script Include classes, and client scripts for ServiceNow scripting. Use for Business Rules, Scheduled Jobs, server-side Script Includes, and client-side g_form/g_user scripts — including the script bodies inside Fluent SDK metadata definitions. Metadata definition itself belongs to sn-sdk-fluent.
Use when working with ServiceNow Fluent DSL (.now.ts files) — generating, reviewing, or explaining metadata definitions for tables, ACLs, business rules, UI pages, client scripts, script includes, flows, service portal widgets, and other ServiceNow metadata types. Covers all 6 column types, all $id-required types, and scope prefix reading from now.config.json.
Use when setting up, configuring, building, or deploying with the ServiceNow SDK — scaffolding new projects, configuring Basic or OAuth authentication, converting existing applications, building and deploying to an instance, or validating a development environment. Covers all init templates, auth setup with named aliases, the build→deploy→verify lifecycle, and the check-environment script.
ServiceNow delivery, requirements, and scope-management best practices for running an implementation well. Use when writing or reviewing user stories, defining acceptance criteria, running requirements workshops, estimating with story points, managing a product backlog, controlling scope (scope creep, change requests, enhancements vs defects), planning sprints and releases, running phase gates, or setting up a delivery quality review. Trigger on: user story, acceptance criteria, INVEST, backlog, epic, theme, sprint, story points, scope checkpoint, scope creep, change request, enhancement, defect, UAT, requirements workshop, phase gate, RIDAC/RAID, delivery methodology, Now Create, engagement manager, BPC, technical consultant, definition of ready, definition of done. Use even when a methodology isn't named but the task is about getting requirements right and keeping a project's scope, budget, and timeline aligned.
ServiceNow platform and instance governance knowledge. Use when defining a governance model, standing up a governance board/committee, setting development standards and coding conventions, managing update sets and CI/CD promotion, managing environments (dev/test/prod) and clones, controlling scope creep and customization vs configuration, enforcing security and least-privilege, planning upgrades and release adoption, or putting guardrails around citizen development / low-code. Trigger on: governance, platform owner, system administrator, update set, instance scan, HealthScan, upgrade, clone, environments, dev/test/prod, coding standards, naming convention, technical debt, customization vs configuration, ACL, least privilege, citizen development, center of excellence, CoE, guardrails. Use even when "governance" isn't named but the task is about keeping a ServiceNow instance controlled, traceable, secure, and clean.