scriptorium

Create auditable doctrine content from informal architectural rules.

2|Updated Mar 10, 2026

Search Tags:#architecture #documentation #audit #pattern #cross-reference #doctrine

Ready to run

npx skills add https://github.com/ppryde/pip-skills --skill scriptorium

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scriptorium
Source: https://github.com/ppryde/pip-skills/tree/main/plugins/puritan/skills/scriptorium
Command: npx skills add https://github.com/ppryde/pip-skills --skill scriptorium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to convert informal architectural rules into codified, auditable doctrines that can be reviewed and enforced.

Core Features & Use Cases

Standardized doctrine templates for architectural patterns and anti-patterns.
Research-driven drafting with cross-references to related doctrines.
Generates a complete blueprint including structure, sources, and validation steps.

Quick Start

Draft a new doctrine by compiling pattern intent, research sources, and cross-references into a formal draft.

Frequently Asked Questions about scriptorium

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

FAQPage Schema

How do I convert informal architectural rules into auditable doctrine documents?▼

To draft an auditable architecture doctrine, you compile pattern intent, research sources, and cross-references into a formal template featuring sections for context, sources, detection signatures, and validation steps.

What is an architecture doctrine and when do I need to codify software patterns?▼

An architecture doctrine is a codified, auditable document that standardizes software patterns and anti-patterns. You need to codify patterns when your team requires enforceable, reviewable rules for consistent architectural decisions.

What should be included in an architecture doctrine template for cross-referencing patterns?▼

An architecture doctrine template should include sections for context, research sources, cross-references to related doctrines, and detection signatures to ensure the pattern is auditable and enforceable across the project.

Can I audit existing software architecture anti-patterns using standardized doctrine drafts?▼

Yes, you can audit existing software architecture anti-patterns by drafting standardized doctrines that include detection signatures and validation steps, allowing teams to formally review and enforce architectural compliance.

What's the best way to structure architectural pattern research for cross-reference planning?▼

The best way to structure architectural pattern research is to use a formal doctrine blueprint that maps pattern intent, research sources, and cross-references, ensuring all informal rules are converted into codified, auditable content.

Do I need a specific template format to document software architecture doctrines?▼

Yes, you need a standard template containing sections for context, sources, cross-references, and detection signatures to generate a complete architecture doctrine blueprint with validation steps.