# C10 Business-Process Tooling Integration — Design

**Date:** 2026-05-17
**Topic:** Populate the empty `C10 «Бизнес-процессы (общее)»` map section.
**Deciders:** Дмитрий
**Method:** `superpowers:brainstorming` (economy 5%). Approach 3 (hybrid + vendoring) approved 2026-05-17; Decision 1 (n8n-mcp DEFERRED) + Decision 2 (vendored BPMN skill) approved 2026-05-17.

---

## Goal

Populate the empty `C10 «Бизнес-процессы (общее)»` section of `docs/automation-graph.html`
with a conflict-minimal business-process toolset — so C10 becomes a working playbook,
the same way A6 «Архитектура систем» was closed with adr-kit/mermaid/architecture-patterns,
C9 «Управление проектами» with the CCPM stack, and A3 «Интеграции» with
openapi-mcp-server + cross-references.

C10 must cover **all three subcategories** of business-process work (user choice
2026-05-17): process **modeling**, workflow **automation**, and process **analysis &
optimization**.

## Context

- **C10 is empty.** `SECTIONS` in `docs/automation-graph.html:2020` defines
  `C10 = «Бизнес-процессы (общее)»` (bucket C «Бизнес-домены»); `NODE_SECTION` tags
  **zero** nodes to C10.
- **The map is a tooling map** — «карта dev-автоматики» (plugins / skills / MCP /
  hooks Claude uses). C10 must therefore be populated with **business-process
  *development tools*** — tooling Claude uses to model/automate/analyse processes —
  not with portal product features.
- **C10 is the catch-all of bucket C.** It sits next to already-populated sections
  whose tools genuinely touch business processes: C9 «Управление проектами»
  (CCPM, product-management), E2 «Оркестрация Claude-воркфлоу» (superpowers, ruflo),
  A6 «Архитектура» (mermaid diagrams). Significant C10 coverage is therefore
  delivered by **cross-references** of those tools — the A3 precedent.
- **The portal's process engine is Laravel.** Лидерра runs business-process
  automation through the Laravel queue (Redis) + events/jobs (deal-pipeline state
  transitions, reminders, `CsvReconcileJob`, `ResetMonthlyCountersCommand`). There is
  **no n8n / external workflow engine** in the stack.
- **The machine is runtime-minimal by policy.** Native Windows, no Docker. Every new
  runtime / MCP server passes an explicit weighing.

## Scope decision

C10 covers **modeling + automation + analysis** (user choice 2026-05-17). Strategy =
**Approach 3 (hybrid + vendoring)**: marketplace plugin where a verified one exists,
**self-authored vendored skills** for niches with no verified marketplace tool,
**cross-references** of existing tools, and one **deferred** workflow-engine slot.

The **n8n-mcp workflow engine is deferred** (Decision 1): the portal stack has no
n8n, the process engine is Laravel; adopting n8n is an architecture decision (ADR),
not a tooling pick. The automation subcategory is *not* left empty — internal
process automation is *designed* via state-machine modeling (the process-modeling
skill) and Claude-side workflow is covered by the ruflo/`writing-plans` cross-refs.
n8n-mcp is registered as a reserved slot, mirroring Figma MCP #44 (DEFERRED) and the
A11 Jupyter MCP severable task.

The **BPMN tool is a self-authored vendored skill** (Decision 2), not a community
mcpmarket skill — provenance under project control, the mermaid-skill / CCPM pattern.

---

## Architecture — the 9-position C10 coverage (Approach 3)

Three subcategories. Three positions are **new** (1 marketplace plugin + 2 vendored
skills), one is **new + deferred**, five are **reuse** cross-references (already
installed — C10 documents the coverage via `NODE_SECTION_SECONDARY`, the A3 XREF
pattern).

| # | Tool | Subcategory | Install mode | Status |
|---|---|---|---|---|
| 1 | **operations plugin** (`operations@knowledge-work-plugins`, Anthropic) | modeling + analysis | new — marketplace plugin (`anthropics/knowledge-work-plugins`, same marketplace as #42 product-management / #46 design) | new, active |
| 2 | **process-modeling skill** | modeling | new — self-authored vendored standalone skill into `.claude/skills/process-modeling/` (no plugin, no marketplace, no hooks — the mermaid/CCPM vendoring pattern) | new, active |
| 3 | **process-analysis skill** | analysis | new — self-authored vendored standalone skill into `.claude/skills/process-analysis/` | new, active |
| 4 | **n8n-mcp** (`czlonkowski/n8n-mcp`, MIT) | automation | new — MCP server, `.mcp.json` | **severable / conditional — DEFERRED** until n8n is adopted as portal infrastructure (separate ADR) |
| 5 | **mermaid skill** (A6 #37) | modeling (render) | already installed — map node `mermaid_skill` in A6 | reuse — cross-ref |
| 6 | **architecture-patterns skill** (A6 #38) | modeling (DDD) | already installed — map node `arch_patterns` in A6 | reuse — cross-ref |
| 7 | **CCPM** (C9 #41) | analysis (traceability) | already installed — map node `ccpm` in C9 | reuse — cross-ref |
| 8 | **product-management plugin** (C9 #42) | modeling + analysis | already installed — map node `product_mgmt` in C9 | reuse — cross-ref |
| 9 | **superpowers writing-plans** | modeling (decomposition) | already installed — map node `sk_wplans` in E2 | reuse — cross-ref |

**New layer (positions 1-3).**

- **operations plugin** = business-process documentation (`/ops:process-doc` —
  document a process with a flowchart), change management (`/ops:change-request`),
  capacity planning (`/ops:capacity-plan`), vendor review (`/ops:vendor-review`).
  Primary C10 tool; touches modeling + analysis. Anthropic-built, same marketplace
  as the already-integrated #42 / #46 — verified provenance.
- **process-modeling skill** = BPMN 2.0 notation (pools, lanes, gateways, events),
  process maps, customer-journey / value-stream maps, RACI matrices. Renders through
  the mermaid skill (BPMN1). Knowledge + workflow skill, zero runtime.
- **process-analysis skill** = process discovery (reverse-engineer the as-is process
  from code + audit-log tables), bottleneck analysis, requirements→process
  traceability, business-process KPI/metrics. Distilled methodology skill — the
  `audit-portal` pattern.

**Deferred (position 4).** n8n-mcp = a workflow engine for the n8n platform. Gated on
an architecture decision to adopt n8n. `.mcp.json` is untouched in the core scope.

**Reuse layer (positions 5-9).** mermaid = render process diagrams (flowchart/state);
architecture-patterns = DDD bounded contexts as process boundaries, domain events as
steps; CCPM = PRD→epic→issue requirements→process traceability; product-management =
`/write-spec` process specs + `/synthesize-research` / `/metrics-review` analysis;
writing-plans = decompose a process into steps. These nodes **stay in their home
sections** and are surfaced in C10 via `NODE_SECTION_SECONDARY` (XREF1).

C10 is **fully covered** by positions 1-3 + 5-9 from day one; position 4 is a
reserved, registered-but-not-installed slot.

---

## Conflict audit

Pattern follows the AK1–CC1 / ML1–ML9 audits of the A6 / C9 / D3 / A11 plans. Full
audit with locked resolutions is produced in the implementation plan; the known
conflicts:

| # | Tool | Sev | Conflict | Resolution direction |
|---|---|---|---|---|
| OPS1 | operations | 🟢 | `/ops:process-doc` produces a flowchart; the mermaid skill (A6) renders diagrams — overlapping render. | operations emits **Mermaid source**; the mermaid skill stays the render-SoT. operations = the *document* + methodology, mermaid = the *rendering primitive*. No dup. |
| OPS2 | operations | 🟢 | `/ops:capacity-plan` overlaps product-management `/sprint-planning` (C9) and C8 HR. | Boundary by scope: operations capacity-plan = cross-functional business-process capacity; `/sprint-planning` = dev-team sprints; C8 = HR. Documented in `docs/process/README.md`. |
| OPS3 | operations | 🟢 | `/ops:change-request` overlaps adr-kit (A6) and claude-md-management. | Distinct objects: change-request = business-process change; ADR = architecture decision; claude-md-management = normative-doc edit. |
| OPS4 | operations | 🟡 | knowledge-work-plugins are built primarily for "Claude Cowork" — must verify the plugin activates in Claude Code. | Plan pre-flight check (`claude plugin` install + slash-command availability). Strong precedent: #42 product-management and #46 design from the **same marketplace** are already integrated and work in Claude Code. |
| BPMN1 | process-modeling | 🟢 | Overlap with the mermaid skill. | mermaid does flowchart/state, **not** BPMN 2.0 (pools/lanes/gateways/XML). Different notation. process-modeling owns BPMN methodology and calls mermaid for rendering. |
| LINT1 | process-modeling, process-analysis | 🟡 | Self-authored skills `.claude/skills/process-{modeling,analysis}/**/*.md` are English technical content → trip the cspell + markdownlint pre-commit jobs (the project cspell dict is RU-focused). | Decided in plan: add both skill dirs to `cspell.json` `ignorePaths` (English skill content) — the MK1 pattern used for vendored mermaid-skill / CCPM. markdownlint treatment confirmed against how existing project skills (`audit-portal`, `regression`) are handled. |
| PA1 | process-analysis | 🟢 | Overlap with perf-analyzer / `analysis:bottleneck-detect` and product-management `/metrics-review`. | Different objects: process-analysis = *business-process* discovery/optimization; perf-analyzer / bottleneck-detect = *code/runtime* performance; `/metrics-review` = *product* metrics. Boundary documented. |
| N8N1 | n8n-mcp | 🟡 | Portal stack has no n8n; the process engine is the Laravel queue. Adopting n8n = architecture decision, not a tooling pick. | **DEFERRED** (Decision 1) — registered as a reserved slot; `.mcp.json` untouched in core scope. Activation gated on a dedicated ADR. |
| XREF1 | reuse layer | 🟢 | Re-tagging `mermaid_skill`/`arch_patterns`/`ccpm`/`product_mgmt`/`sk_wplans` to C10 would empty their home sections — `NODE_SECTION` is 1-node→1-section. | Reuse nodes **stay** in their sections; C10 surfaces them via `NODE_SECTION_SECONDARY` (the A3 precedent). C10 gets its own 3 new nodes. |
| CAT1 | all | 🟢 | C10 is non-UI tooling. | New off-phase category **business-process** (a new off-phase subcategory; exact ordinal resolved in the plan against the live registry), outside the PSR_v1 UI-pool — no R6.0/R6.1 stack-filter, no R14 pipeline — same as architecture-tooling (A6) / audit-security (D3) / project-management (C9). |
| BUS1 | all | 🟡 | Bus-factor — operations is Anthropic; the two skills are self-authored; n8n-mcp is community. | operations = Anthropic, verified, stable. process-modeling / process-analysis = **self-authored vendored** → immune to upstream loss (the mermaid-skill pattern). n8n-mcp = community (czlonkowski, ~16.6k★, MIT) but **deferred** + version-pinned at install time. |
| NUM1 | all | 🟡 | C10's Tooling-registry numbers depend on the live counter (A6, D3, C9, A3, A4, A11 already landed). | Numbers runtime-resolved: the plan reads the **live** `docs/Tooling_v8_3.md` Прил. Н §0 counter and assigns C10's numbers sequentially. |

---

## File structure

| File | Created / Modified | Responsibility |
|---|---|---|
| `docs/process/` | Create dir | C10 home — the business-process playbook |
| `docs/process/README.md` | Create | The BP convention: tool boundaries (operations = *document / change / capacity* · process-modeling = *model* BPMN · process-analysis = *discover & optimize* · n8n-mcp = *deferred engine*); the reuse-layer cross-ref map; a worked example modeling one real Лидерра process (deal lifecycle or supplier reconciliation) |
| `.claude/skills/process-modeling/` | Create (self-authored vendored) | The process-modeling skill — `SKILL.md` + `references/` (BPMN 2.0, process maps, journey/value-stream, RACI) |
| `.claude/skills/process-analysis/` | Create (self-authored vendored) | The process-analysis skill — `SKILL.md` + `references/` (process discovery, bottleneck, traceability, BP metrics) |
| `docs/adr/ADR-NNN-business-process-tooling.md` | Create | Seed ADR documenting the C10 tooling decision + the n8n defer. **NNN runtime-resolved** against live `docs/adr/` (ADR-006 = a4-design-tooling exists; next free resolved in plan) |
| `cspell.json` | Modify | `ignorePaths` += the two skill dirs (LINT1) |
| `.markdownlintignore` | Modify (conditional — per LINT1 decision) | += the two skill dirs if markdownlint treatment requires it |
| `cspell-words.txt` | Modify (conditional) | New business-process vocabulary if any RU terms trip cspell |
| `docs/Tooling_v8_3.md` | Modify | Прил. Н — new business-process subsection(s) + §0 counter bump |
| `docs/Plugin_stack_rules_v1.md` | Modify | R10.1 — new business-process rows (operations = Block 1 marketplace plugin; vendored skills = note; n8n-mcp = Block 3 MCP, DEFERRED) |
| `docs/Pravila_raboty_Claude_v1_1.md` | Modify | §13.2 — business-process category note |
| `CLAUDE.md` | Modify (**via claude-md-management only**, §5 п.10) | §3 title count, §1 row 2b count, new §3.3 business-process rows, §6 + §9 entries |
| `docs/CHANGELOG_claude_md.md` | Modify | CLAUDE.md version-bump entry |
| `docs/automation-graph.html` | Modify | 3 new C10 nodes → `NODE_SECTION` C10; 5 cross-refs → `NODE_SECTION_SECONDARY`; header metrics |
| `.mcp.json` | **NOT modified in core scope** | n8n-mcp deferred — `.mcp.json` touched only by the conditional task |

**Map nodes.** C10 gets **3 new nodes** — `ops_plugin`, `process_modeling`,
`process_analysis` → `NODE_SECTION` C10. Five reuse nodes (`mermaid_skill`,
`arch_patterns`, `ccpm`, `product_mgmt`, `sk_wplans`) are surfaced via
`NODE_SECTION_SECONDARY` → `['C10']` (XREF1). An `n8n_mcp` node is added only when
the conditional task runs (same as A11's deferred `jupyter_mcp`).

---

## Severable scope

**Core C10** = operations plugin + the 2 vendored skills + the 5 reuse cross-refs +
normative sync + map closure. This already populates and closes the section across
all three subcategories.

**Conditional / severable** = the n8n-mcp install (position 4) — a separate task,
gated on an architecture decision (a dedicated ADR) to adopt n8n as portal
infrastructure. Registered now as a reserved slot; installed later.

C10 adds **no lefthook job** and **no `.mcp.json` change** in the core scope — fewer
conflicts by design (the C9 shape).

---

## Out of scope

- Building actual business-process automation features into the CRM product
  (deal-pipeline automations, reminder workflows) — that is product work, tracked
  separately; C10 only provides the *tooling*.
- Adopting n8n (or any external workflow engine) as portal infrastructure — the
  n8n-mcp conditional task, gated on its own ADR.
- Any business-process-modeling gate in the commit pipeline (no lefthook job).

## Open items resolved by the implementation plan

- **NUM1** — C10's Tooling-registry numbers are runtime-resolved against the live
  `docs/Tooling_v8_3.md` Прил. Н §0 counter (after A6 / D3 / C9 / A3 / A4 / A11).
- **ADR number** — resolved against live `docs/adr/` (ADR-006 exists; the next free
  number is assigned).
- **OPS4** — the plan's pre-flight verifies the operations plugin activates in Claude
  Code (install + slash-command check).
- **LINT1** — the plan decides the exact cspell / markdownlint treatment of the two
  self-authored skills by inspecting how existing project skills are handled.
- **Sequencing** — C10 forks off the **live** `origin/main` (currently `008c8a3`,
  A11 landed). This spec's worktree branch is a scratch branch; execution re-forks if
  `origin/main` has moved.
- **Exact tool identity** — operations plugin id / marketplace path and n8n-mcp
  repo/version verified via WebFetch/WebSearch in the plan's Tool Identity section
  (the A6/C9/D3/A11 pattern).
