How do I install the Architecture Session Playbook skill?

Run npx skillmds@latest add konradcinkusz/architecture-session-playbook 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 Architecture Session Playbook 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 Architecture Session Playbook?

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 Architecture Session Playbook free to use?

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

Who published Architecture Session Playbook?

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

Architecture Session Playbook by konradcinkusz

Name: Architecture Session Playbook
Author: konradcinkusz

Architecture Session Playbook

Use when starting an architecture review or modernization of a repo, or when unsure which mode a repo needs. Chooses between REVIEW (already broadly compliant), MODERNIZE (predates the architecture but builds) and RECOVER (does not build, or source and dependencies are partly lost), states which documents each mode must produce, which guides to load for which domain, and why RECOVER begins with archaeology rather than design.

konradcinkusz Updated Sep 17, 2026

File contents

Architecture Session Playbook

Read references/PLAYBOOK.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
Session prompt template
What to attach to the session
Choosing REVIEW vs MODERNIZE
Output conventions

Why this exists

docs/architecture/00-REFERENCE-ARCHITECTURE.md in this repo is the one architectural constitution for the estate: 15 principles, each backed by a working example in copilot-scope or the reference SaaS, plus a compliance checklist. It must not be re-derived from scratch in every session — an agent should read it, not reconstruct it from first principles each time.

Two systems already broadly follow it, with known deviations catalogued:

copilot-scope/docs/architecture/ARCHITECTURE_REVIEW.md
<saas>/docs/architecture/ARCHITECTURE_REVIEW.md

The legacy monorepo predates the architecture and is being modernized toward it; its docs/architecture/ directory (00-SECURITY-IMMEDIATE.md … 07-STANDARDS-FEEDBACK.md) is the worked example of what a RECOVER session produces.

Generated from docs/PLAYBOOK.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: architecture-session-playbookdescription: Use when starting an architecture review or modernization of a repo, or when unsure which mode a repo needs. Chooses between REVIEW (already broadly compliant), MODERNIZE (predates the architecture but builds) and RECOVER (does not build, or source and dependencies are partly lost), states which documents each mode must produce, which guides to load for which domain, and why RECOVER begins with archaeology rather than design.---# Architecture Session Playbook**Read [`references/PLAYBOOK.md`](references/PLAYBOOK.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- Session prompt template- What to attach to the session- Choosing REVIEW vs MODERNIZE- Output conventions## Why this exists[`docs/architecture/00-REFERENCE-ARCHITECTURE.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/architecture/00-REFERENCE-ARCHITECTURE.md)in this repo is the one architectural constitution for the estate: 15 principles, eachbacked by a working example in copilot-scope or the reference SaaS, plus a compliancechecklist. It must not be re-derived from scratch in every session — an agent shouldread it, not reconstruct it from first principles each time.Two systems already broadly follow it, with known deviations catalogued:- `copilot-scope/docs/architecture/ARCHITECTURE_REVIEW.md`- `<saas>/docs/architecture/ARCHITECTURE_REVIEW.md`The legacy monorepo predates the architecture and is being modernized toward it; its`docs/architecture/` directory (`00-SECURITY-IMMEDIATE.md` … `07-STANDARDS-FEEDBACK.md`)is the worked example of what a RECOVER session produces.---Generated from [`docs/PLAYBOOK.md`](https://github.com/konradcinkusz/architecture-standards/blob/main/docs/PLAYBOOK.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

Architecture Session Playbook

File contents

Architecture Session Playbook

What this standard covers

Why this exists

Related skills

Frequently asked questions

How do I install the Architecture Session Playbook skill?

What does the Architecture Session Playbook skill do?

Is Architecture Session Playbook safe to use?

Which AI agents work with Architecture Session Playbook?

Is Architecture Session Playbook free to use?

Who published Architecture Session Playbook?