jonasvanderhaegen

Designing Advanced Release-Management Flows

A Reusable Prompt for LLM-Assisted System Design

---

1. How to use this prompt

Paste Section 9 ("The prompt") into any capable LLM and replace the bracketed parameters with your application's domain, platform constraints, and team conventions. The remaining sections are reference material: read them before customising the prompt so you understand the concepts being referenced. The models below are derived from Google Play Console and App Store Connect; they generalise to any system where an artifact must pass through composition, validation, review, and staged deployment.

---

jonasvanderhaegen

MCP: the complete option surface

Research notes (June 2026). Everything an MCP implementation can offer, on both sides of the wire: the primitives, the utilities, the transports, authorization, and where the protocol is heading (the 2026-07-28 release candidate changes the picture substantially). Companion to the deep-dive notes on resources, prompts, and the LSP comparison.

Spec versions to date: 2024-11-05, 2025-03-26 (Streamable HTTP, OAuth), 2025-06-18 (elicitation, structured tool output, resource indicators), 2025-11-25 (current

jonasvanderhaegen

## Advisor

Call advisor() BEFORE substantive work: before writing, before committing to an approach. Reading files to orient is fine first.

Also call when stuck (errors recurring, approach not converging), when changing approach, or when the task is complete, though first make deliverables durable (write file, commit).

Skip when you are already running as Opus, since advisor() would be Opus consulting itself, or when this turn immediately follows a completed /plan session, since the plan output already serves as the advisor input.

On longer tasks: once before committing to approach, once before declaring done. Don't call after every step: advisor adds most value before the approach crystallizes.

jonasvanderhaegen

use std::env;
use std::path::{Path, PathBuf};

fn link_mode() -> &'static str {
    if env::var("LBUG_SHARED").is_ok() {
        "dylib"
    } else {
        "static"
    }
}