execution-monitoring
CSA guardrail scanner for execution monitoring: audits committed architecture decisions against live dependency state, flags technical constraint breaches and unresolved blockers. Produces a punch-list for delivery integrity. Chains with task-hygiene-flow and unified-constraint-check for SE morning prep. Triggers: guardrail scanner, architecture breach, dependency audit, CSA punch-list, constraint violation, owner-motion mismatch, execution blockers.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Purpose
Provides CSA with a risk-classified view of committed milestones, surfacing execution blockers, architecture constraint violations, and owner-motion mismatches that threaten delivery.
Freedom Level
Medium — Risk classification requires judgment; corrective actions are role-specific.
Trigger
- Daily/weekly execution sweep for committed scope
- User asks "what's at risk?" or "execution status"
- Pre-governance preparation
Flow
- Call
msx-crm:crm_auth_status. - Call
msx-crm:get_my_active_opportunities— single call for all active opportunities. - Call
msx-crm:get_milestoneswithopportunityIds(batch from step 2),statusFilter: 'active', andincludeTasks: true— one call returns committed milestones with inline tasks. If scoped to a single customer, usecustomerKeywordinstead. - Classify execution state per milestone.
- Generate dry-run corrections:
-
msx-crm:update_milestonefor risk/status/comments -
msx-crm:create_taskfor follow-up actions
-
Execution State Classification
| State | Criteria |
|---|---|
| On track | Active tasks with owners, no blockers, date >30 days |
| At risk | Date <30 days with incomplete tasks OR missing delivery motion |
| Blocked | No active tasks, no recovery plan, OR owner-motion mismatch detected |
| Owner mismatch | CSA listed as owner but delivery motion is Partner/ISD/Unified |
Decision Logic
- Owner-motion mismatch → flag for reassignment, do not absorb delivery PM work
- Technical blockers → CSA-actionable, produce remediation plan
- Delivery/resourcing blockers → route to CSAM or delivery owner
- Commercial/scope issues → route to Specialist
- Escalate when no recovery activity exists for near-term committed milestone
Output Schema
-
risk_dashboard: milestone-level status with reason codes -
remediation_plan: owner + action + due date per item -
owner_mismatch_flags: milestones needing ownership clarification -
dry_run_operations: update/task preview payloads -
next_action: "Execution sweep complete. Would you like to runvalue-realization-packfor milestones approaching delivery completion?"
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-03-11
- Index updated
- 2026-03-11
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!