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.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
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.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Compare competing customer use cases by value, feasibility and evidence. Use when several problems compete for delivery capacity.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Map stakeholders, decision rights, influence and blockers from supplied evidence. Use when ownership is unclear or the stakeholder landscape changes.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Assess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Prepare a customer demo or executive walkthrough around an evidenced outcome. Use before show-and-tell to rehearse the journey and prepare a fallback.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Draft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
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.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Plan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Evaluate an AI workflow against representative cases and its permitted actions. Use for model, retrieval or agent evaluation; tests do not grant release authority.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Assess a field lesson for reuse or product feedback without exposing customer context. Use for recurring deployment lessons; distinguish a hypothesis from a validated pattern.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use for delivery planning, estimation or migration strategy.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
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.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Choose up to three immediate priorities from competing initiatives. Use when everything is urgent and the customer needs a defensible order with explicit deferrals.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Prepare a sponsor update separating promised outcomes, measured results and customer acceptance. Use for progress readouts or defending a delivery claim.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Triage an outage, loss of stakeholder trust or a failing engagement direction. Use for urgent recovery; distinguish diagnosis from authorized production mitigation.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
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.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Prepare and rehearse a recovery path for an intended release. Use when rollback is assumed, untested or previously failed; follow the environment authority for any drill.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Assess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Prepare or execute an authorized controlled release with verified checks, recovery and an operating owner. Use when a customer increment is ready for deployment.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026
Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.
The English summary is being prepared. Showing the original description.
suboss87/FDEOps☆ 970Updated Oct 9, 2026