scena-doctor

Automate scena doctor checks to enforce governance rules and log waivers.

18|1|Updated May 7, 2026

Search Tags:#architecture #validation #gates #checks #silent-failure #doctor #scena

Ready to run

npx skills add https://github.com/johannesPettersson80/scena --skill scena-doctor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scena-doctor
Source: https://github.com/johannesPettersson80/scena/tree/main/.codex/skills/scena-doctor
Command: npx skills add https://github.com/johannesPettersson80/scena --skill scena-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scena Doctor protects project health by enforcing known checks and governance rules, preventing silent drift and regressions as the project evolves.

Core Features & Use Cases

Enforces documentation, architecture, and gate-rule consistency across code changes.
Provides a repeatable review workflow for adding, changing, or reviewing scena doctor checks.
Use Case: When updating library modules, run the doctor to ensure new changes comply with the established rules and documentation requirements.

Quick Start

Automatically run the doctor checks during development and prior to handoff to catch issues early.

Frequently Asked Questions about scena-doctor

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

FAQPage Schema

How do I prevent silent architecture drift across project codebases?▼

Preventing silent architecture drift requires running automated doctor checks during development and handoff to enforce governance rules, documentation, and gate artifacts across codebases.

What is a scena doctor check and when should I run it?▼

A scena doctor check is an automated validation that enforces architecture, documentation, and gate-rule consistency. You should run it during development and prior to handoff to catch compliance issues early.

How do I validate governance requirements and log rule waivers with traceable evidence?▼

To validate governance requirements, the doctor check enforces established rules and logs waivers with traceable evidence, providing clear outcomes for architectural compliance across codebases.

Can I use automated architecture checks to enforce documentation consistency when updating library modules?▼

Yes, you can run the doctor to ensure new changes to library modules comply with established rules and documentation requirements, maintaining architecture and gate-rule consistency.

What's the best way to enforce gate artifacts and architecture rules across multiple codebases?▼

The best way to enforce gate artifacts and architecture rules is applying a repeatable review workflow that validates checks automatically, preventing regressions as the project evolves.