docs-keeper

Audit codebase architecture against canonical doctrine and repository implementation.

Updated Aug 23, 2026

Search Tags:#architecture #audit #repository #governance #alignment #boundaries #doctrine

Ready to run

npx skills add https://github.com/Deadpool042/Creatyss --skill docs-keeper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-keeper
Source: https://github.com/Deadpool042/Creatyss/tree/main/.agents/skills/docs-keeper
Command: npx skills add https://github.com/Deadpool042/Creatyss --skill docs-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams verify that architectural decisions and domain boundaries align with the canonical doctrine and the actual repository implementation.

Core Features & Use Cases

Targeted architectural audits
Boundary and cadrage verification
Gap analysis between doctrine and repo
Stakeholder-aligned recommendations

Quick Start

Review the current architecture and doctrine alignment to generate a scoped improvement plan.

Frequently Asked Questions about docs-keeper

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

FAQPage Schema

How do I audit architecture against canonical doctrine in a repository?▼

To audit architecture against canonical doctrine, compare the intended domain boundaries with the actual repository implementation. Identify deltas between doctrine and reality, then propose minimal, scoped actions to restore alignment.

What is architectural boundary verification and when do I need it?▼

Architectural boundary verification checks if domain alignments and cadrage of lots conform to canonical doctrine. You need it when identifying deltas between planned architecture and the real repository implementation.

How do I identify deltas between doctrine and repo implementation?▼

Identify deltas between doctrine and repo by performing a targeted architectural audit. Compare domain alignments and boundaries in the codebase against the canonical doctrine to spot discrepancies.

Does architectural audit work without predefined doctrine documents?▼

Architectural audit requires canonical doctrine documents to function properly. Without predefined doctrine, the audit cannot identify deltas or propose scoped actions to restore domain alignment within the repository.

What's the best way to generate scoped improvement plans for architecture governance?▼

The best way to generate scoped improvement plans for architecture governance is to audit the repository against canonical doctrine. This identifies deltas and proposes minimal, targeted actions to restore alignment.

How do I verify domain alignment within my codebase?▼

Verify domain alignment within your codebase by applying a targeted architectural audit. Compare the real repository implementation against canonical doctrine to identify deltas and propose scoped corrective actions.