Your standards. Built in.Write down how your team builds once. Phyllis follows it, cites the rule, and stays inside your controls.
- Created catalog item New Laptop Request · sc_cat_item · read back
- Reused variable set Laptop Configuration · io_set_item · read back
- Created UI policy “Require accessory details when Other is selected” · catalog_ui_policy · read back
- Created client script “Recommend RAM for laptop model” · catalog_script_client · read back
Build complete — all 4 layers verified. Update set Phyllis - AdHoc - NewLaptopRequest - 2026 left in progress.
- Explored 2 sources · Ran for 33s
Short answer: the P2 “breaches” mostly come from duplicated SLA definitions piling clocks onto a queue nobody owns, not from slow resolution on one clock.
Stacked SLA definitions. Several overlapping SLA sets attach to P2 incidents, so one late P2 shows up as many breaches.
No owner. Of the 36 active P2 incidents, 33 have no assignee.
Wrong SLAs attached. “IT Support P1/P3 — Resolution” clocks are attached to P2 incidents.
- Explored 43 sources, wrote 1 document · Ran for 3m 46s
The assessment is done and the full report is in the Artifacts panel. It scores the CMDB 57/100 (Poor, D).
Nothing on the instance was changed.
- Explored 11 sources · Ran for 3m 40s
A rebuilt, single canonical “Travel Request” catalog item and its full fulfilment lifecycle — order form, tiered approvals, Travel Desk booking and notifications.
33 stories across 7 epics, each with effort, points and acceptance criteria.
- Ran suite SPM — Regression Suite · TES0001108 · 1 minute
The suite ran on acmedev: 8 passed, 0 failed. Each test and its result is open beside the chat, with the run record.
- Previewed on acme-test · No conflicts · health checks clean
Previewed the update set on acme-test — no conflicts. Seven records are captured, all in the right scope.
Promote Phyllis - AdHoc - NewLaptopRequest - 2026 to acme-test? Approve
- Explored 23 sources · Read your team conventions
The Build Book lists the skills and team conventions I’m following, and every reference resolved on your instance before anything is built.
Built for how ServiceNow teams work
- ISO 27001 certified
- Per-user OAuth
- No training on your data
- Scoped update sets
- Jira · Agile 2.0
Conventions applied, and cited
Before anything is built, the Build Book lists the skills and team conventions Phyllis is following — and every reference it resolved on your instance.
Best Practice Studio
Every convention, accelerator and prompt book your team uses, in one place — Phyllis’s library, your edited versions and your own. Switch each one on per instance — or per customer, for partners.
Start from the standards you already have
Upload your development standards. Phyllis routes each passage to the right domain and drafts conventions cited to the passages they came from — nothing applies until an admin accepts it.
Governance, in your own words.Set the rules once in Best Practice Studio. Then ask her what’s in force, and why she built it the way she did.
“Which conventions are in force here?”
Scope“Why did you name it u_warranty_expiry?”
Cited“Build the approval the way our standards say.”
Applied“Can you write to acme-prod?”
Instance accessNothing ships without your approval.
Signs in as you.
Per-user OAuth — she inherits your roles and ACLs, and every change is logged under your name.
ApprovalsApproval on every change.
Approval cards before changes are written — one at a time, or the whole approved build. Nothing reaches production from chat.
ApprovalsPer-instance controls.
Build, Read-only or Backlog only per instance. Table rules and switched-off tools are enforced on every request.
ApprovalsQuestions & Answers
What is Best Practice Studio?
One place for the conventions, accelerators and prompt books your team uses — Phyllis’s library, your edited versions and your own — each switched on per customer or instance.
Can I import our existing standards?
Yes. Upload the document and Phyllis drafts conventions from it, each line cited to the passage it came from. An admin reviews and accepts them before they apply.
What happens when Phyllis updates the library?
Items you use as-is pick up the new text. Items you edited keep your version — the change is shown to you, never applied silently.
How do I know which rules she followed?
Every chat shows the conventions in force, and Phyllis cites the convention she applied in her answer.
Get started with Govern.
See it on your own instance in thirty minutes.