How do I install the Master Delivery Prompt skill?

Run npx skillmds@latest add konradcinkusz/master-delivery-prompt in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Master Delivery Prompt safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Master Delivery Prompt?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Master Delivery Prompt free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Master Delivery Prompt?

konradcinkusz (@konradcinkusz) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Master Delivery Prompt by konradcinkusz

Name: Master Delivery Prompt
Author: konradcinkusz

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.

konradcinkusz Updated Sep 17, 2026

File contents

The master delivery prompt

Read 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 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 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.

---name: master-delivery-promptdescription: 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.---# 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 decidewhether 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 andRECOVER each produce documents and deliberately stop short of code. But the estate alsohas a recurring *delivery* job — "review the whole app against my standards, adopt theexternal auth service, bring the frontend in line, document the UI/UX, and leave theproduct running on Fly.io" — and until now that job description was rewritten by handfor each repo, with the repo name hardcoded into the prompt. This is the one genericversion: 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 ofthem. Everything the playbook says about choosing REVIEW vs MODERNIZE vs RECOVER stillapplies.---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.

Frequently asked questions