fde-engagement-lifecycle

Guides Forward Deployed Engineering engagements from customer discovery through production handoff.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/miyake-san/sogo-agent-platform --skill fde-engagement-lifecycle-miyake-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fde-engagement-lifecycle
Source: https://github.com/miyake-san/sogo-agent-platform/tree/main/skills/experimental/fde-engagement-lifecycle
Command: npx skills add https://github.com/miyake-san/sogo-agent-platform --skill fde-engagement-lifecycle-miyake-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Customer-facing proof-of-concept and embedded engineering work often fails due to unclear problem framing, missing stakeholder alignment, and demos that never convert to production. This Skill provides a structured lifecycle that keeps Forward Deployed Engineering engagements on track from first discovery call to final handoff. ## Core Features & Use Cases - Discovery and Problem Framing: Runs 8-10 discovery questions to identify decision makers, operators, data owners, and security owners, then defines the value hypothesis, baseline, success metric, and explicit non-goals. - Gated Prototype and Demo Workflow: Enforces spec, RFC, Excalidraw, and ADR gates before building a narrow tracer-bullet prototype, then prepares a deterministic demo with seeded data, golden identifiers, reset, and fallback. - Pilot and Production Handoff: Defines time-boxed pilots with owners, metrics, telemetry, and exit criteria, then produces a handoff package covering gaps, risks, runbook, architecture, and backlog. - Use Case: An engineer embedded with a customer uses this Skill to structure a six-week POC, ensuring the demo is reproducible and the pilot has clear stop criteria before committing to production. ## Quick Start Use the fde-engagement-lifecycle skill to plan and run my upcoming customer POC from discovery through production handoff.

Frequently Asked Questions about fde-engagement-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a Forward Deployed Engineering engagement?

Follow an eight-step lifecycle: run discovery questions to map stakeholders, frame the problem with a value hypothesis and success metric, pass spec and ADR gates, build a tracer-bullet prototype, prepare a deterministic demo, run a time-boxed pilot, and deliver a production handoff.

How to structure a customer POC that converts to production?

Define explicit non-goals and a measurable success metric upfront, build a narrow prototype against realistic interfaces, and run a time-boxed pilot with owners, telemetry, exit criteria, and stop criteria before committing to production work.

What should a production handoff document include after a pilot?

A production handoff should contain identified gaps, risks, a runbook, architecture documentation, key decisions, a remaining backlog, a support model, and accountable owners for each area.

When is the FDE lifecycle approach not appropriate?

This lifecycle is designed for customer-facing POCs and embedded engineering work. It is heavier than needed for internal tooling, solo experiments, or mature products where discovery and pilot gating add little value.