myITprocess QBR Prep
Overview
A QBR in myITprocess is a meeting record (myitprocess_meetings_list) with the
recommendations the vCIO wants to discuss on its agenda. The brief this skill
produces gives the vCIO the client's current position and the decisions to ask
for, in one page. It uses only Conduit read tools; none is admin-gated, and
nothing here can create or edit the meeting or its agenda (that is done in
myITprocess).
See api-patterns for filters and the rate limit,
alignment-reviews for review status, and
roadmap for recommendation, finding and budget fields.
Anti-triggers
- A cross-vendor QBR built as a value conversation (PSA ticket stats, RMM,
security tooling, MSP Value Pyramid levels 3-5) — use the wyre-gateway
plugin's QBR prep agent; it can take this skill's brief as its vCIO roadmap
input.
Key Concepts
Meetings (myitprocess_meetings_list)
| Field |
Notes |
status |
Upcoming, InProgress, Past, Cancelled |
title, purpose, summaryDescription, location |
Free text set by the vCIO |
startDate, endDate |
Meeting time |
client.id, client.name |
The client |
createdBy.fullName |
Usually the vCIO |
| agenda recommendation IDs |
Array; returned but not filterable |
Common Workflows
One-client QBR brief
- Client.
myitprocess_clients_list with name contains the client
name; confirm the match. Keep id, alignmentScore, lastReviewDate.
- Meeting.
myitprocess_meetings_list filtered by client.id, sorted by
startDate desc. Take the next Upcoming meeting as the one being
prepared, and the most recent Past meeting as the baseline for "since last
time". If there is no upcoming meeting, say so and prepare against today.
- Recommendations.
myitprocess_recommendations_list filtered by
client.id and isArchived equal false; page to totalCount. Mark the
ones whose id is in the upcoming meeting's agenda. If an item on the last
past meeting's agenda is not in that list, repeat the call with isArchived
equal true and report it as archived in "Since last meeting".
- Initiatives.
myitprocess_initiatives_list filtered by client.id and
isArchived equal false, to group recommendations under their initiative
titles.
- Reviews and gaps.
myitprocess_reviews_list filtered by client.id;
myitprocess_reviews_overdue_categories_list filtered by client.id; and
for the latest completed review, myitprocess_findings_list filtered by its
review.id and findingType equal UnassignedReviewFinding.
That is six to eight calls for one client, well inside the 50 per minute limit.
Brief layout
- Header — client, meeting title, date, purpose, vCIO.
- Position — alignment score, last review date, open review and its status,
number of standards categories due or overdue (the tool does not separate
the two).
- Since last meeting — agenda items from the last
Past meeting and their
status now (Completed, InProgress, still NotDiscussed).
- Decisions to ask for — agenda recommendations that are
NotDiscussed or
OnHold, highest priority first, with budget, budget month, hours and
responsible party.
- Roadmap by initiative — remaining open recommendations grouped by
initiative; budget totals for the next two to four quarters, committed
(
Accepted, InProgress) separate from proposed (NotDiscussed).
- Gaps without a plan — unassigned findings from the last review, by
question.label. Mark this section internal: findings describe security
gaps.
- Next review — the categories due or overdue, as the scope to schedule.
Keep sections that have nothing in them, with a one-line "none", so the reader
knows the data was checked.
Meetings calendar (portfolio)
myitprocess_meetings_list filtered status equal Upcoming, sorted by
startDate ascending. Cross-check myitprocess_clients_list (active clients)
for clients with no upcoming meeting and an old lastReviewDate: those are the
QBRs that have not been booked.
Gotchas
- Agenda IDs are not filterable. Fetch the client's recommendations once and
match IDs locally; do not query recommendations one by one.
summaryDescription on past meetings is the vCIO's own note. Quote it as
written; do not paraphrase it into commitments the client did not make.
- Read-only. If the user asks to add an item to the agenda or mark a
recommendation accepted after the meeting, say that it is done in myITprocess;
this connector cannot write.
1---2name: myitprocess-qbr-prep3description: >4 Assembling a one-client brief from myITprocess before a QBR or strategy5 meeting: the meeting record and its agenda recommendations, the client's6 alignment score and review history, open and recently changed7 recommendations, budget for the coming quarters, initiatives, and open review8 gaps. Also covers a meetings calendar across clients. Read-only.9when_to_use: >-10 When preparing for a client QBR, business review or strategy meeting from11 myITprocess data, or listing upcoming and past client meetings. Use when:12 myitprocess qbr, qbr prep, business review prep, vcio meeting prep, meeting13 agenda, upcoming client meetings, or strategy meeting.14metadata:15 source: https://skillmd.com/skills/wyre-ai/myitprocess-qbr-prep16---1718# myITprocess QBR Prep1920## Overview2122A QBR in myITprocess is a meeting record (`myitprocess_meetings_list`) with the23recommendations the vCIO wants to discuss on its agenda. The brief this skill24produces gives the vCIO the client's current position and the decisions to ask25for, in one page. It uses only Conduit **read** tools; none is admin-gated, and26nothing here can create or edit the meeting or its agenda (that is done in27myITprocess).2829See [api-patterns](../api-patterns/SKILL.md) for filters and the rate limit,30[alignment-reviews](../alignment-reviews/SKILL.md) for review status, and31[roadmap](../roadmap/SKILL.md) for recommendation, finding and budget fields.3233## Anti-triggers3435- **A cross-vendor QBR built as a value conversation** (PSA ticket stats, RMM,36 security tooling, MSP Value Pyramid levels 3-5) — use the wyre-gateway37 plugin's QBR prep agent; it can take this skill's brief as its vCIO roadmap38 input.3940## Key Concepts4142### Meetings (`myitprocess_meetings_list`)4344| Field | Notes |45|-------|-------|46| `status` | `Upcoming`, `InProgress`, `Past`, `Cancelled` |47| `title`, `purpose`, `summaryDescription`, `location` | Free text set by the vCIO |48| `startDate`, `endDate` | Meeting time |49| `client.id`, `client.name` | The client |50| `createdBy.fullName` | Usually the vCIO |51| agenda recommendation IDs | Array; returned but not filterable |5253## Common Workflows5455### One-client QBR brief56571. **Client.** `myitprocess_clients_list` with `name` `contains` the client58 name; confirm the match. Keep `id`, `alignmentScore`, `lastReviewDate`.592. **Meeting.** `myitprocess_meetings_list` filtered by `client.id`, sorted by60 `startDate` `desc`. Take the next `Upcoming` meeting as the one being61 prepared, and the most recent `Past` meeting as the baseline for "since last62 time". If there is no upcoming meeting, say so and prepare against today.633. **Recommendations.** `myitprocess_recommendations_list` filtered by64 `client.id` and `isArchived` `equal` `false`; page to `totalCount`. Mark the65 ones whose `id` is in the upcoming meeting's agenda. If an item on the last66 past meeting's agenda is not in that list, repeat the call with `isArchived`67 `equal` `true` and report it as archived in "Since last meeting".684. **Initiatives.** `myitprocess_initiatives_list` filtered by `client.id` and69 `isArchived` `equal` `false`, to group recommendations under their initiative70 titles.715. **Reviews and gaps.** `myitprocess_reviews_list` filtered by `client.id`;72 `myitprocess_reviews_overdue_categories_list` filtered by `client.id`; and73 for the latest completed review, `myitprocess_findings_list` filtered by its74 `review.id` and `findingType` `equal` `UnassignedReviewFinding`.7576That is six to eight calls for one client, well inside the 50 per minute limit.7778### Brief layout79801. **Header** — client, meeting title, date, purpose, vCIO.812. **Position** — alignment score, last review date, open review and its status,82 number of standards categories due or overdue (the tool does not separate83 the two).843. **Since last meeting** — agenda items from the last `Past` meeting and their85 status now (`Completed`, `InProgress`, still `NotDiscussed`).864. **Decisions to ask for** — agenda recommendations that are `NotDiscussed` or87 `OnHold`, highest `priority` first, with budget, budget month, hours and88 responsible party.895. **Roadmap by initiative** — remaining open recommendations grouped by90 initiative; budget totals for the next two to four quarters, committed91 (`Accepted`, `InProgress`) separate from proposed (`NotDiscussed`).926. **Gaps without a plan** — unassigned findings from the last review, by93 `question.label`. Mark this section internal: findings describe security94 gaps.957. **Next review** — the categories due or overdue, as the scope to schedule.9697Keep sections that have nothing in them, with a one-line "none", so the reader98knows the data was checked.99100### Meetings calendar (portfolio)101102`myitprocess_meetings_list` filtered `status` `equal` `Upcoming`, sorted by103`startDate` ascending. Cross-check `myitprocess_clients_list` (active clients)104for clients with no upcoming meeting and an old `lastReviewDate`: those are the105QBRs that have not been booked.106107## Gotchas108109- **Agenda IDs are not filterable.** Fetch the client's recommendations once and110 match IDs locally; do not query recommendations one by one.111- **`summaryDescription` on past meetings is the vCIO's own note.** Quote it as112 written; do not paraphrase it into commitments the client did not make.113- **Read-only.** If the user asks to add an item to the agenda or mark a114 recommendation accepted after the meeting, say that it is done in myITprocess;115 this connector cannot write.