GFE Valuation Suite Template

Template Type: System Architecture
Source: GFE Skill System Suite Docs (/docs/valuation-ops/[LAYER]/[SUITE].md)
Goal: Aggregate related flows into a cohesive functional suite.
Use with: .agent/workflows/create-suite-post.md

---

0. SCHEMA EXTRACTION GUIDE

Before writing, extract these fields from the Suite markdown:

Required Fields

• Suite Name: (e.g., "Lead Gen Suite")
• Layer: (e.g., "Revenue Ops")
• Flows: List of all flows (e.g., "Digital Lead Gen", "Social Selling").
• Objectives: The goal of each flow.

Auto-Fetch Related Data

1. Process Details:

• For each Flow, extract the Process ID (e.g., PROC-REV-OUTBOUND-EMAIL-01).
• Link: /blog/posts/[process-slug]

2. Key Tasks:

• Extract key tasks listed for each flow (M/S/F).
• Link: /blog/posts/[task-slug]

3. KPIs:

• Extract "Primary KPIs" listed for each flow.
• Link: /blog/posts/[kpi-slug]

---

1. ARTICLE STRUCTURE

Frontmatter

---
title: '[Suite Name] Architecture'
slug: [suite-slug]-overview
date: '[YYYY-MM-DD]T00:00:00.000Z'
description: >-
  [Suite Name]. The complete architecture of [Flow Count] flows driving [Layer Name].
author: GFE Strategy Lab
image: /images/blog/[suite-slug]-hero.png
alt: [Hero image description]
tags:
  - valuation-ops
  - [layer-slug]
  - suite
sections:
  - gfe-systems
  - valuation-ops
featured: false
aside: true
footer: true
traceability:
  valuationLayer: [layer-slug]
  suiteId: [Suite Name]
  processIds: [array of process IDs]
head:
  - - meta
    - name: robots
      content: 'index, follow'
  - - meta
    - property: 'og:title'
      content: '[Suite Name] Architecture'
  - - meta
    - property: 'og:description'
      content: >-
        [Suite Name]. The complete architecture.
  - - meta
    - property: 'og:image'
      content: '/images/blog/[suite-slug]-hero.png'
  - - meta
    - property: 'og:type'
      content: 'article'
---

---

Section 1: Hook — The Functional Engine (150-200 words)

Purpose: Define this suite's specific job in the valuation stack.

Template:

# [Suite Name] Architecture

**ValuationOps Layer: [[Layer Name]](/blog/posts/[layer-slug])**

In the GFE Skill System, the **[Suite Name]** is responsible for [Function, e.g., "filling the top of the funnel"].

It is not enough to have "some marketing." You need a structured set of flows that systematically [Goal]. This suite contains [Count] canonical flows designed to [Outcome].

::: tip Suite Stats
- **Flows**: [Count]
- **Key Processes**: [Count]
- **Primary KPIs**: [List top 3]
:::

![Suite visualization](/images/blog/[suite-slug]-hero.png)

---

---

Section 2: The Flow Map (Visual)

Purpose: Show the flows within this suite.

Template:

## The Flow Map

We structure the [Suite Name] into [Count] distinct flows:

```mermaid
graph LR
    Suite[[[Suite Name]]]
    
    subgraph "Category 1"
    F1([Flow 1])
    F2([Flow 2])
    end
    
    subgraph "Category 2"
    F3([Flow 3])
    F4([Flow 4])
    end
    
    Suite --> F1
    Suite --> F2
    Suite --> F3
    Suite --> F4

---

---

### Section 3: Flow Deep Dives (500-800 words)

**Purpose:** Breakdown each flow.

**Template:**
```markdown
## 1. [Flow Name]
**Objective:** [Objective from doc]

**Process:** [[Process ID]](/blog/posts/[process-slug]) *(coming soon)*

This flow orchestrates:
- **Marketing**: [[Task ID]](/blog/posts/[task-slug])
- **Sales**: [[Task ID]](/blog/posts/[task-slug])
- **Finance**: [[Task ID]](/blog/posts/[task-slug])

**Primary KPIs:**
- [[KPI Name]](/blog/posts/[kpi-slug])

---

## 2. [Flow Name]
...

---

Section 4: Traceability Chain

Template:

## Traceability Chain

**Upstream Layer:** [[Layer Name]](/blog/posts/[layer-slug])

**Component Processes:**
[For each Process:]
- [[Process ID]: [Process Name]](/blog/posts/[process-slug])

---

---

Section 5: FAQ (3-5 Questions)

Template:

## FAQ

**Q: Which flow should I start with?**  
A: [Recommendation based on maturity].

**Q: Who owns this suite?**  
A: [Role].

---

---

2. WRITING GUIDELINES

Tone Strategy

Functional & Tactical:

• Focus on capabilities and coverage.
• Use terms like "Micro-system," "Channel," "Motion."

Visuals:

• The Mermaid diagram should show the flows branching from the suite.

---

3. IMAGE GENERATION

Subject Formula:

• "Abstract diagram of [Suite Name] showing multiple streams or channels"
• "Hub and spoke visualization"

Base Prompt:

Minimalist 3D relief illustration on off-white background. Muted teal (#1AA8A0) accent. Subject: [SUBJECT]. Composition: branching, flowing, connected, negative space. Typography: "[Suite Name]" in clean sans, dark slate. Lighting: soft top-front. 16:9 aspect ratio.

Save To: docs/public/images/blog/[suite-slug]-hero.png

---

4. FINAL CHECKLIST

• [ ] Suite schema extracted
• [ ] Flows mapped to Processes
• [ ] Key Tasks linked
• [ ] KPIs linked
• [ ] Hero image generated

---

End of Template