suboss87

Clarify a new customer brief, desired outcome, constraints and evidence gaps. Use for kickoff or a first meeting; do not repeat discovery already supplied.

Configure or diagnose access to a requested source using available host tools. Use for source MCP setup; source configuration needs no engagement record and credentials stay with the host.

Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.

Turn meeting notes or a transcript into sourced decisions, changes and next actions. Use after a customer conversation; review consequential record updates before saving.

Prepare a customer demo or executive walkthrough around an evidenced outcome. Use before show-and-tell to rehearse the journey and prepare a fallback.

Fetch requested source material and prepare sourced engagement updates. Use to catch up from external notes or messages; applying updates requires a bound record and confirmation.

Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.

Compare feasible approaches to a customer problem and recommend a path with costs, constraints and evidence. Use for an architecture or delivery decision, not implementation.

Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use for delivery planning, estimation or migration strategy.

Run a bounded customer proof of concept to test a consequential uncertainty. Use for a spike or pilot with a question and decision deadline, not a full rollout.

Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.

Prepare a sponsor update separating promised outcomes, measured results and customer acceptance. Use for progress readouts or defending a delivery claim.

Triage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.

Review a proposed customer code change against its intended outcome and operational risks. Use for a diff or PR review; report evidence and actionable findings.

Audit an inherited engagement or implementation against its evidence

Draft a board or executive summary of an engagement using outcomes, risks and investment decisions

Develop a business case for an initiative using costs, benefits, risks and evidence

Choose up to three immediate priorities from competing initiatives

Stress-test a plan, brief or delivery claim against evidence and plausible failure modes

Prepare and rehearse a recovery path for an intended release

Write an operating runbook from the delivered system and verified procedures

Assess a new customer request against agreed scope, trade-offs and ownership

Compare competing customer use cases by value, feasibility and evidence

Switch between existing customer engagements and triage competing needs

Challenge a proposed solution by identifying and testing consequential assumptions

Map stakeholders, decision rights, influence and blockers from supplied evidence

Plan how to earn customer trust and appropriate access