etkm-crm-doctrine

Define fixed Pipedrive CRM doctrine governing pipelines, stages, labels, and transitions.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-crm-doctrine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: etkm-crm-doctrine
Source: https://github.com/easttxkravmaga/Claude/tree/main/archive/etkm-crm-doctrine
Command: npx skills add https://github.com/easttxkravmaga/Claude --skill etkm-crm-doctrine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ETKM CRM management in Pipedrive requires a fixed architectural reference to ensure consistent handling of pipelines, stages, labels, and transitions across the client lifecycle.

Core Features & Use Cases

  • Fixed, multi-pipeline architecture that aligns with the five-stage lifecycle from Prospect to Specialize.
  • Clear governance for promotions, label retention, and handoffs between pipelines, with explicit rule sets and event triggers.
  • Reference framework for automation mechanics, data integrity, and change control across the ETKM CRM stack.

Quick Start

Load this doctrine as the canonical CRM reference before any client lifecycle decisions in Pipedrive.

Frequently Asked Questions about etkm-crm-doctrine

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

FAQPage Schema
How do I standardize Pipedrive pipeline stages and labels across the client lifecycle?

A fixed CRM doctrine standardizes Pipedrive pipelines by defining required stages, labels, and transitions across the entire client lifecycle. It serves as the canonical reference for maintaining consistent pipeline architecture.

What is a CRM doctrine for managing pipeline transitions and governance?

A CRM doctrine is a fixed architectural reference that governs pipeline promotions, label retention, and handoffs. It enforces consistent structure by specifying explicit rule sets, event triggers, and automation mechanics for change control.

Can I use this CRM doctrine to manage multiple pipelines from Prospect to Alumni in Pipedrive?

Yes, this doctrine defines a fixed multi-pipeline architecture that aligns with the five-stage lifecycle from Prospect to Specialize. It explicitly governs handoffs, promotions, and label retention across all client lifecycle stages in Pipedrive.

How do I set up automation rules and data integrity controls for Pipedrive pipelines?

You set up Pipedrive automation rules by applying a fixed CRM doctrine that specifies required references, dependencies, and event triggers. This framework provides the governance mechanics needed to maintain data integrity across CRM updates.

When do I need a fixed architectural reference for Pipedrive pipeline management?

You need a fixed architectural reference when managing client lifecycle decisions that require consistent handling of pipelines, stages, labels, and transitions. Load this CRM doctrine as the canonical reference before making any Pipedrive updates.