engineering-doctrine

Define and document engineering doctrines and guiding principles for technical projects.

1|Updated Jan 5, 2026
One-click install
npx skills add https://github.com/mattg101/SolidLink --skill engineering-doctrine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engineering-doctrine
Source: https://github.com/mattg101/SolidLink/tree/main/docs/dev/.agent/skills/engineering-doctrine
Command: npx skills add https://github.com/mattg101/SolidLink --skill engineering-doctrine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps in defining and documenting the core engineering principles and doctrines for a project or organization.

Core Features & Use Cases

  • Doctrine Definition: Clearly articulate the guiding principles for engineering practices.
  • Documentation: Provides a structured way to record and share these principles.
  • Use Case: A new engineering team lead can use this skill to quickly establish and document the foundational engineering doctrine for their team.

Quick Start

Use the engineering-doctrine skill to define the core principles for our new AI project.

Frequently Asked Questions about engineering-doctrine

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

FAQPage Schema
How do I document engineering principles for a new software project?

To document engineering principles, you articulate the guiding doctrines and core values for your software project. This provides a structured way to record and share foundational guidelines for system architecture and team practices.

What is an engineering doctrine and when do I need one?

An engineering doctrine is a set of documented guiding principles and operational tenets for technical projects. You need one to establish foundational guidelines for software development, system architecture, and team practices.

How do I establish foundational guidelines for a new engineering team?

You establish foundational guidelines for an engineering team by defining core values and operational tenets. Documenting these engineering doctrines provides a structured framework to quickly align team practices and technical project execution.

What is the best way to define technical project doctrines and core values?

The best way to define technical project doctrines is by clearly articulating your core values and operational tenets. Structuring these engineering principles into a documented format ensures they can be effectively shared and followed across the organization.

Can I use this to create guidelines for system architecture and team practices?

Yes, you can use it to create guidelines for system architecture and team practices. The process involves defining engineering doctrines that articulate the guiding principles applicable to establishing foundational rules for your software development environment.