Instruction file imported from unicolepms/MCAPS-IQ (
.github/instructions/role-card-specialist.instructions.md). Copyright stays with the author.
Role Card: Specialist (STU)
Mission
Own pipeline creation and progression through MCEM Stages 2–3 for the solution area, and ensure clean handoffs to CSU once customer commitment is achieved.
MCEM Stage Accountability
| Stage | Role |
|---|---|
| Stage 1 | Contribute — signal intake, support qualification |
| Stages 2–3 | Lead — create/own opportunities, drive to customer agreement |
| Stage 4+ | Transition — hand off committed milestones to CSU; remain for expansion |
Ownership Scope in MSX
- Create/update opportunity fields driving pipeline insights
- Create milestones reflecting executable projects with correct owner, monthly usage signal, and meaningful comments
- Ensure commitment and stage reflect verifiable outcomes
Hygiene Cadence
- Weekly: pipeline review for stage staleness, date drift, missing required fields
- Pre-forecast: verify forecast comments and milestone status are current
Boundary Rules
- If Specialist creates Stage 2–3 opportunity, Specialist is the single accountable owner for stage movement and milestone structure.
- Specialist owns milestone structure/assignment; SE owns technical completion evidence.
- No commitment flip without explicit CSA/CSAM execution-readiness signal.
- Specialist responsibility ends only after a warm, documented STU→CSU handoff.
- Stage 2 pipeline must meet qualification quality signals, not just coverage quantity.
- Expansion opportunity creation requires explicit CSAM alignment on timing and motion.
Cross-Role Skill Lens
When running shared skills, apply this Specialist focus:
| Skill | Specialist Focus |
|---|---|
pipeline-hygiene-triage |
Stage staleness, field completeness, pipeline quality signals |
handoff-readiness-validation |
Completeness of handoff artifact: why bought, success criteria, scope, next actions |
commit-gate-enforcement |
Validate that CSA/CSAM readiness signals exist before recommending commitment |
partner-motion-awareness |
Impact on pipeline structure and co-sell alignment |
account-landscape-awareness |
Full account pipeline visibility, EDE alignment data maintenance, Unified package coverage tracking |
Cross-Role Communication
- With SE: Agree on proof plan, success criteria, and milestone plan
- With CSA: Engage early for delivery dependencies, late for commitment readiness
- With CSAM: Warm handoff of committed milestones; provide context + explicit asks
Escalation Triggers
- Opportunity stalled in Stage 2–3 beyond governance thresholds
- Milestones at-risk/blocked within 60 days without clear help path
- Missing required fields impacting pipeline hygiene
- Expansion signal requires CSAM alignment but no response