# Master Delivery Prompt

> Use when running a delivery session against an application repo — one that must end aligned to the standards AND live as a workable product. The generic fill-in prompt covering, in phases: the assessment (a playbook mode plus gap analysis against the compliance checklist), adopting the external authservice as the system's only identity provider, bringing the frontend to a Next.js product surface under the frontend/BFF rules, comprehensive UI/UX documentation with a ranked backlog, shipping every service to Fly.io, and an optional parallel Azure provisioning job. States what to attach, the read-only scope of the standards and authservice repos, and the definition of done.

- Skill: `konradcinkusz/master-delivery-prompt` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add konradcinkusz/master-delivery-prompt`
- Raw SKILL.md: https://api.skillmd.com/api/skills/konradcinkusz/master-delivery-prompt/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: konradcinkusz (https://skillmd.com/u/konradcinkusz)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/konradcinkusz/master-delivery-prompt

---


# The master delivery prompt

**Read [`references/MASTER-PROMPT.md`](references/MASTER-PROMPT.md) before applying any of this.**
That file is the standard; everything below it is a summary to help you decide
whether this skill applies and to check your work afterwards.

## What this standard covers

- Why this exists
- The prompt
- Fill-in reference
- What to attach to the session
- What a finished session leaves behind
- A note on the frontend framework

## Why this exists

[`PLAYBOOK.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/PLAYBOOK.md) covers the documentation sessions: REVIEW, MODERNIZE and
RECOVER each produce documents and deliberately stop short of code. But the estate also
has a recurring *delivery* job — "review the whole app against my standards, adopt the
external auth service, bring the frontend in line, document the UI/UX, and leave the
product running on Fly.io" — and until now that job description was rewritten by hand
for each repo, with the repo name hardcoded into the prompt. This is the one generic
version: fill in the target block, attach the three repos, run it.

A delivery session does not replace the playbook modes — its first phase *is* one of
them. Everything the playbook says about choosing REVIEW vs MODERNIZE vs RECOVER still
applies.

---

Generated from [`docs/MASTER-PROMPT.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/MASTER-PROMPT.md) by `scripts/build-marketplace.mjs`. Do not edit this file: change the source document, or its entry in `catalog/marketplace.catalog.json`, and re-run the generator.