Subash Natarajan

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

日本語の概要は準備中です。原文の説明を表示しています。

Compare competing customer use cases by value, feasibility and evidence. Use when several problems compete for delivery capacity.

日本語の概要は準備中です。原文の説明を表示しています。

Map stakeholders, decision rights, influence and blockers from supplied evidence. Use when ownership is unclear or the stakeholder landscape changes.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Keeps the engagement record for client work. Use when they name a client or stakeholder. Use when they debrief a meeting or paste notes. Use when they ask what was agreed. Use when they run a POC, change the client's codebase, prove it on their staging, go live, or need evals before a model acts. Use when they prep a readout, when trust shifts, or they say @fde. Route and run the local fde CLI (or npx --yes fdeops). Never ask them to type commands. Not for ordinary code edits in an unbound repo.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Transfer operation of a customer deployment with ownership, evidence and a tested support path. Use for handoff or an engineer rotation, not merely code delivery.

日本語の概要は準備中です。原文の説明を表示しています。

Audit an inherited engagement or implementation against its evidence. Use when taking over work or joining mid-project; distinguish verified facts from inherited claims.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Plan how to earn customer trust and appropriate access. Use when credibility, permissions or AI policy constrain the engagement.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate an AI workflow against representative cases and its permitted actions. Use for model, retrieval or agent evaluation; tests do not grant release authority.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Stress-test a plan, brief or delivery claim against evidence and plausible failure modes. Use when the user asks for a red team or preparation for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

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

日本語の概要は準備中です。原文の説明を表示しています。

Write an operating runbook from the delivered system and verified procedures. Use when the customer team or a successor needs to operate without the original engineer.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare or execute an authorized controlled release with verified checks, recovery and an operating owner. Use when a customer increment is ready for deployment.

日本語の概要は準備中です。原文の説明を表示しています。