staircase-book-triage

Staircase Book Triage (CSM cockpit)

A CSM opens Monday with a full book and three hours. This skill turns the whole book into one ranked "do this first" list: not a health dashboard, an action queue. It reads every motion at once (risk that's loud, risk that's silent, renewals with a clock, coverage that's one-deep, accounts gone quiet, expansion that's heating) and hands back the few accounts that actually need the CSM this week, each with the one next move.

The architecture (why it's cheap): ONE owner-scoped report pulls the ~14 signal columns for the whole book; every lens below is a client-side filter over that single pull. No per-account calls to build the list; those are reserved for the drill on the few accounts the CSM picks.

This is the single-book lens. For the portfolio/leader view use ../staircase-risk-radar/; for one account's deep read use ../staircase-account-deep-dive/ or ../staircase-risk-check/; to plan renewals specifically use ../staircase-renewal-watchlist/. A manager prepping for a 1:1 with a teammate (personal effort/overwhelmed test + this same book, from the manager's chair) should use ../staircase-1on1-prep/ instead. It reuses this skill's 7-motion table by reference rather than duplicating it.

Foundation references (read BEFORE composing any query)

• ../staircase-mcp-expert/ + ../staircase-mcp-expert/references/advanced-report-patterns.md: the report engine, the argument system, owner scoping, field ids, and the reliability rules in ../staircase-mcp-expert/references/anti-patterns.md.
• ../staircase-app-design/: the interactive-cockpit standard (see the visual section).
• ../../_shared/staircase-output-best-practices.md: house style, evidence discipline, no CRM writes.
• User profile (if present): ~/.staircase-mcp/user-profile.md, the CSM's identity / owner scope.

Scope (decide first)

• Use the resolved book-owner field. customer.owner is not always the CSM; on some orgs it holds a different role and the real book lives on another field. Read scope.book_owner_field from ~/.staircase-mcp/user-profile.md; if absent, run the foundation's first-call contract (../staircase-mcp-expert/SKILL.md step 0, recipe scope.membership), which computes it and asks only when ambiguous. Use that field for all scoping below.
• Self (the default): customer.<book_owner_field> In [current_user_id] (or Equal <id> for a custom Reference field). current_user_id comes from report_metadata and is exact. This is how the CSM running the skill scopes to their own book.
• A named CSM (a manager looking at one rep, or when the profile names someone): customer.<book_owner_field>.full_name In ["<name>"] in run_report. A bare name on the Reference field itself errors; go through the .full_name leaf, or use the person's user.id.
• Portable fields only. Never hardcode a specific _c field id. The confirmed book-owner field is a runtime parameter, discovered per org, not baked into this skill.