Verified:GitHub

doctrine

Load project doctrine and filter governance rules for the assigned task.

26|3|Updated Oct 9, 2025

Search Tags:#decision making #governance #spec-driven development #architecture alignment #project doctrine #risk avoidance

Ready to run

npx skills add https://github.com/davidlee/spec-driver --skill doctrine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doctrine
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/doctrine
Command: npx skills add https://github.com/davidlee/spec-driver --skill doctrine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Doctrine prevents teams from making decisions based on assumptions, guesses, or duplicated interpretations of governance rules.

Core Features & Use Cases

Identify articles of truth: Locate the governing documents that define how the project should be understood and evolved.
Apply governance to tasks: Use doctrine to decide what matters for your specific assignment before proceeding.
Avoid governance failure modes: Reduce risks like assumption, guesswork, duplication, architectural infidelity, and heretical coupling.

Quick Start

Ask the agent to read the project doctrine hook and summarize the articles of truth relevant to your current task.

Frequently Asked Questions about doctrine

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

FAQPage Schema

How do I ensure architecture decisions align with project governance rules?▼

To avoid governance mistakes, load your project's authoritative doctrine material from a configured hook document to filter guidance and warn against architectural infidelity before proceeding with any architecture decisions.

What is project doctrine and when do I need it for spec-driven development?▼

Project doctrine is the authoritative rule set that prevents governance mistakes by avoiding assumptions, guesswork, and duplicated interpretations. You need it during spec-driven development to ensure task scoping aligns with project truth.

How do I apply project governance to task scoping and incremental changes?▼

Apply project governance by instructing the agent to read the doctrine hook document and summarize the articles of truth relevant to your assignment, filtering guidance to only what matters for your specific task.

How do I prevent duplicated interpretations of governance rules across my team?▼

Prevent duplicated interpretations by using a centralized doctrine hook document that defines how the project should be understood and evolved, ensuring all team members reference the same articles of truth.

What are common governance failure modes in architecture alignment?▼

Common governance failure modes include assumption, guesswork, duplication, architectural infidelity, and heretical coupling. Project doctrine helps identify and avoid these risks before executing incremental changes.

Does project doctrine work without predefined reference documents?▼

No, project doctrine requires a configured hook document containing your project's doctrine material. It loads these references to locate governing documents and filter meaningful guidance for your assigned tasks.