GFE Skill Task Deep Dive Template

Template Type: Task-Based How-To Guide
Source: GFE Skill System Task Schemas (/spec/tasks/{domain}/{task-id}.json)
Goal: Transform task schemas into actionable, valuation-aware how-to guides for practitioners.
Use with: .agent/workflows/create-skill-task-post.md

---

0. SCHEMA EXTRACTION GUIDE

Before writing, extract these fields from the task JSON:

Required Fields

{
  "id": "F-001",
  "domain": "finance",  // M (marketing), S (sales), F (finance)
  "level": 2,           // 0-4 (Observer, Operator, Designer, Strategist, Architect)
  "title": "Build monthly cash flow forecast",
  "description": "...",
  "category": "Planning",
  "valuation_channel": "cashflow_ops",  // Maps to ValuationOps layer
  "process_bundle": "Cash Flow Ops",
  "kpi_links": ["KPI-CF-001", "KPI-CF-002"],
  "proof_types": ["forecast_model_link", "assumption_sheet"],
  "gfe_mapping": "0.1.2"  // Maps to Canon Laws
}

Auto-Fetch Related Data

1. KPI Details (from /spec/metrics/kpi-definitions.json): For each ID in kpi_links[], fetch:

• name, description, formula, frequency, owner, valuation_link

2. Related Process (from /spec/processes/): Search for process where name or description contains process_bundle:

• Extract: steps[], primary_kpis[], okrs[], tooling

3. ValuationOps Layer (from /docs/valuation-ops/): Map valuation_channel to blog post URL:

• revenue_ops → /blog/posts/revenue-ops-overview
• ebitda_ops → /blog/posts/ebitda-ops-overview
• cashflow_ops → /blog/posts/cashflow-ops-overview
• etc.

4. Related OKRs (reverse lookup in /spec/okrs/): Find OKRs where:

• key_results[].kpi_id matches any KPI in kpi_links[]
• OR process okrs[] contains this OKR

5. Canon Laws (from gfe_mapping):

• Map to Law 1-10 blog posts (e.g., Law 7 blog post)
• If valuation_channel = cashflow_ops, auto-link to Law 7 (Processes → KPIs → Valuation)

---

1. ARTICLE STRUCTURE

Frontmatter

---
title: 'How to [Task Title in Plain English]'
slug: [task-id-kebab-case]
date: '[YYYY-MM-DD]T00:00:00.000Z'
description: >-
  [Task description adapted for SEO - include domain, level, and valuation impact]
author: GFE Strategy Lab
image: /images/blog/[task-id]-hero.png
alt: [Hero image description]
tags:
  - skill-system
  - [domain-name]
  - level-[level-number]
  - [category-lowercase]
sections:
  - gfe-systems
  - skill-tasks
featured: false
aside: true
footer: true
traceability:
  valuationLayer: [valuation_channel]
  suite: [process_bundle-slug]
  okrIds: [extracted-okr-ids]
  kpiIds: [kpi_links array]
  processId: [related-process-id]
  taskIds: [this-task-id]
head:
  - - meta
    - name: robots
      content: 'index, follow'
  - - meta
    - property: 'og:title'
      content: 'How to [Task Title]'
  - - meta
    - property: 'og:description'
      content: >-
        [Task description]
  - - meta
    - property: 'og:image'
      content: '/images/blog/[task-id]-hero.png'
  - - meta
    - property: 'og:type'
      content: 'article'
  - - script
    - type: 'application/ld+json'
    - |
      {
        "@context": "https://schema.org",
        "@type": "HowTo",
        "name": "[Task title as H1]",
        "description": "[Task description from schema]",
        "image": "[Full URL to hero image]",
        "totalTime": "PT[X]H",
        "estimatedCost": {
          "@type": "MonetaryAmount",
          "currency": "USD",
          "value": "0"
        },
        "tool": [
          {
            "@type": "HowToTool",
            "name": "[Tool 1 from process or inferred]"
          }
        ],
        "step": [
          {
            "@type": "HowToStep",
            "name": "[Step 1 heading]",
            "text": "[Brief description of step 1]",
            "position": 1
          },
          ...repeat for all major steps (aim for 5-10 steps)
        ]
      }
---

---

Section 1: Hook — Why This Task Drives Valuation (150-200 words)

Purpose: Connect tactical execution to enterprise value creation.

Template:

# How to [Task Title in Plain English]

Most [domain practitioners] treat [task subject] as [common misconception]. 

That view misses the chain: this task moves [KPI-1] and [KPI-2], which feed [ValuationOps Layer], which capital markets price into your [revenue multiple / EBITDA margin / cash runway].

[One-line hook about why this matters NOW — regulatory change, AI disruption, market conditions]

This guide breaks down the Level [N] [Domain] task **[Task ID]: [Task Title]** — what it is, how to execute it, what deliverables prove mastery, and how it maps to the GFE Canon.

::: tip Who This Is For
- **Level**: [Level Name] (L[N])  
- **Domain**: [Domain Name]  
- **Category**: [Category]  
- **Drives**: [List KPI names]
:::

![{Task title visualization}]({image path from frontmatter})

---

Image Placement: The hero image appears right after the "Who This Is For" tip box to create a visual anchor before diving into task details.

Variables:

• [domain practitioners]: "CFOs", "RevOps Managers", "Growth PMs"
• [task subject]: "cash flow forecasting", "churn analysis", "email sequencing"
• [common misconception]: "a compliance exercise", "a finance-only problem", "a marketing tactic"
• [KPI-1], [KPI-2]: Extracted from kpi_links[]
• [ValuationOps Layer]: Map from valuation_channel
• [revenue multiple / EBITDA margin / cash runway]: Pick based on valuation_channel

---

Section 2: Task Overview (200-300 words)

Purpose: Define the task scope, requirements, and outputs.

Template:

## What This Task Is

**Task ID:** `[id]`  
**Title:** [title]  
**Domain:** [domain] ([M/S/F full name])  
**Level:** [level] ([Level Name])  
**Category:** [category]

[Paste task description from JSON]

### Level Requirements

**Level [N]: [Level Name]** means you are expected to:
- [Level-specific expectations — see LEO model]
- [Learning / Earning / Org-Building balance for this level]

At this level, you [do/design/strategize] [task], with [degree of autonomy].

### What "Done" Looks Like

This task demonstrates mastery through these proof types:

[For each item in `proof_types[]`:]
- **[Proof Type]**: [Human-readable description]

These aren't bureaucratic checkboxes — they're the evidence that you moved the KPIs and reduced internal risk (Law 8: IRI).

Variables:

• Extract directly from task JSON
• Map level to LEO expectations:
  • L0 (Observer): You watch/learn
  • L1 (Operator): You execute with guidance
  • L2 (Designer): You design and execute autonomously
  • L3 (Strategist): You plan multi-task strategies
  • L4 (Architect): You build reusable systems

---

Section 3: Step-by-Step Execution (600-800 words)

Purpose: Tactical how-to guide. This is the meat of the article.

Template:

## How to Execute This Task

[If a related process exists, introduce it:]
This task is part of the **[Process Name]** (`[Process ID]`) workflow. See the [full process walkthrough](/blog/posts/[process-slug]) for orchestration details.

### Prerequisites

Before starting, you need:
- **Tools**: [Extract from related process `tooling[]` if available, else suggest common tools for domain]
- **Data Access**: [Infer from KPI data sources]
- **Skills**: [Map from `level` requirements]

### Step 1: [First Major Step]

[Detailed instructions]

**Common Pitfalls:**
- [Infer from domain expertise or leave empty for user to fill]

### Step 2: [Second Major Step]

[Detailed instructions]

**Example:**
[If possible, provide a worked example using the F-001 cash flow forecast as reference]

### Step 3: [Continue through major steps]

...

### Step [N]: Validation and Handoff

[How to verify the deliverable meets proof standards]

**Checklist:**
- [ ] [Proof type 1] is complete and accessible
- [ ] [Proof type 2] is reviewed by [owner from KPI]
- [ ] [KPI-1] has moved in the expected direction

Guidance:

• If a related process exists, extract steps[] and use task_id references to Show how this task fits
• If no process, infer steps from task description and domain best practices
• Include tactical details: formulas, tooling, templates

---

Section 4: KPI Impact Analysis (300-400 words)

Purpose: Show how this task moves measurable outcomes.

Template:

## KPI Impact: What This Task Moves

This task directly influences:

[For each KPI in `kpi_links[]`:]

### [KPI Name] (`[KPI ID]`)

**What It Is:** [KPI description]

**Formula:**

[KPI formula in plain text]

**Why It Matters:**  
[KPI's connection to valuation via `valuation_link`]

**Owner:** [KPI owner]  
**Frequency:** [KPI frequency]  
**Data Sources:** [List KPI data sources]

**How This Task Improves It:**  
[Explain the causal link — e.g., "By reconciling cash position to revenue forecasts, you reduce variance in Operating Cash Flow, which lowers perceived cash risk and tightens the revenue multiple."]

---

### Related KPIs

This task also indirectly supports:
- [If the related process has `primary_kpis[]`, list those here as well]

::: info Learn More
See the full breakdown: [KPI Name KPI Deep Dive](/blog/posts/kpi-[kpi-id-slug])
:::

Auto-Linking:

• Fetch KPI details from kpi-definitions.json
• Generate slug: kpi- + lowercase KPI ID with hyphens (e.g., kpi-cf-001)
• Link to KPI blog post (to be created later)

---

Section 5: Process and OKR Context (200-300 words)

Purpose: Show where this task fits in the bigger picture.

Template:

## Where This Fits

### Parent Process

**Process:** [Process Name] (`[Process ID]`)

[Brief process description]

**This task is Step [N] of [Total Steps]:**  
[Show the sequence from process `steps[]`:]
1. [Step 1: Task ID - Task Name]
2. **→ [This task]** ← You are here
3. [Step 3: Task ID - Task Name]

**Required Role:** `[role_signature from process step]`  
**Tooling Stack:** [List tooling for this step]

::: tip Full Walkthrough
See [Process Name Walkthrough](/blog/posts/proc-[process-id-slug]) for end-to-end execution.
:::

---

### Supporting OKRs

This task supports these strategic objectives:

[For each related OKR:]

**[OKR ID]:** [Objective]  
**Owner:** [owner_role]  
**Target:** [Key result targets where KPI matches]

::: info OKR Breakdown
Read the full breakdown: [OKR [ID]]( /blog/posts/okr-[okr-id-slug])
:::

Auto-Linking:

• Extract process details if process_bundle matches a process name
• Reverse lookup OKRs where key_results[].kpi_id matches any kpi_links[]
• Generate slugs for process and OKR posts

---

Section 6: ValuationOps Connection (150-200 words)

Purpose: Tie to the ValuationOps stack and GFE Canon.

Template:

## ValuationOps Connection

This task rolls up into the **[ValuationOps Layer Name]** layer of the GFE ValuationOps stack.

**Traceability Chain:**

```mermaid
graph LR
    A[This Task: [Task ID]] --> B[KPI: [Primary KPI]]
    B --> C[[Valuation Layer]: [Layer Name]]
    C --> D[Enterprise Value]

How It Connects: [Explain the value chain — e.g.:]

• You execute this task → [KPI-1] improves
• [KPI-1] feeds into [ValuationOps Layer] reporting
• Capital markets use [Layer] KPIs to price [revenue multiple / margin / risk premium]
• Better execution = lower IRI (Internal Risk Index) = lower WACC = higher valuation

Law 8: Internal Risk Matters

Poor execution of this task increases operational noise, which investors price as risk. Clean, repeatable processes reduce WACC. See Law 8: Reduce Internal Risk.

---

GFE Canon Mapping

Primary Law: [Map from gfe_mapping or infer from valuation_channel]

[Brief explanation of how this task demonstrates the law]

Related Laws:

• [Law 2: ValueLogs] — Time spent on this task should be logged
• [Law 3: Proof Beats Perception] — Proof types demonstrate real activity
• [Law 7: Processes → KPIs → Valuation] — This task is the atomic unit in that chain

Deep Dive

Read Law [N]: [Law Title] for the full breakdown.

**Auto-Linking:**
- Map `valuation_channel` to layer name and blog post URL
- Map `gfe_mapping` to Canon Law (if available)
- Default to Law 7 for all tasks (since tasks → KPIs → valuation)

---

### Section 7: TraceabilityChain Component (Auto-Generated)

**Purpose:** Visual navigation across the full hierarchy.

**Template:**
```vue
<TraceabilityChain
  :valuationLayer="{ name: '[Layer Name]', url: '[layer-url]' }"
  :suite="{ name: '[Suite Name]', url: '[suite-url]' }"
  :okr="{ id: '[OKR ID]', url: '[okr-url]' }"
  :kpis="[
    { id: '[KPI-1]', name: '[KPI-1 Name]', url: '[kpi-url]' },
    { id: '[KPI-2]', name: '[KPI-2 Name]', url: '[kpi-url]' }
  ]"
  :process="{ id: '[Process ID]', name: '[Process Name]', url: '[process-url]' }"
  :tasks="[
    { id: '[Task ID]', name: '[Task Title]', url: '[this-url]' }
  ]"
/>

Note: This component will be created in Phase 0. For now, use a markdown sidebar:

---

## Traceability Chain

**ValuationOps Layer:** [Cash Flow Ops](/blog/posts/cashflow-ops-overview)  
**Process:** [Cash Flow Forecasting](/blog/posts/proc-cashflow-forecast-01)  
**KPIs:**
- [KPI-CF-001: Operating Cash Flow](/blog/posts/kpi-cf-001)
- [KPI-CF-002: Cash Conversion Cycle](/blog/posts/kpi-cf-002)

**OKRs:**
- [OKR-2025-Q1-20: Extend Cash Runway](/blog/posts/okr-2025-q1-20)

**Related Tasks:**
- [M-040: Marketing Data Pull](/blog/posts/m-040)
- [S-041: Sales Forecast Pull](/blog/posts/s-041)

---

---

2. WRITING GUIDELINES

Tone Strategy: Sharp Insight Over Forced Humor

The Balance: These posts serve 600+ schemas. The voice must be distinctive without being exhausting.

Core Principle: Make readers feel SEEN (not entertained). Point out absurdities they live with daily.

---

Hook & Diagnosis (First 200 words): Subvert Expectations

Purpose: Challenge conventional wisdom, frame problems as reveals

Good:

• "Most CFOs treat cash flow forecasting as a compliance exercise" ← Subverts the norm
• "You bought the AI tools. Six months later, performance hasn't moved." ← Pattern they recognize
• "The $50M company with 9 tools, 3 dashboards, and zero forecast accuracy" ← Sharp specificity

Avoid:

• Generic: "Cash flow forecasting is important for businesses"
• Joke-first: "Cash flow forecasting: because crystal balls don't reconcile to GAAP!"
• Academic: "Empirical evidence suggests liquidity management optimization correlates with..."

Template Pattern:

Most [practitioners] treat [task] as [wrong mental model].

That view misses the chain: this task moves [KPI], which feeds [ValuationOps layer], 
which capital markets price into [valuation driver].

[One sharp observation about current state or recent forcing function]

---

Step-by-Step Execution: Clinical Precision

Purpose: Actually help them execute the task tomorrow

Tone: Zero wit. Maximum clarity.

Good:

• "Mixing accrual P&L with cash flow—use the cash flow statement, not the income statement"
• "If your waterfall shows $2,400K at Month 12 but your reconciliation shows $2,100K, you have an error. Hunt it down."

Avoid:

• Jokes during formulas: "DSO is like your ex—the longer it lingers, the more it costs you"
• Clever metaphors: "Think of working capital as the bloodstream of your business"
• Vague hand-waving: "Consider optimizing your collections process"

Rule: When they're executing, be their operator's manual, not their entertainer.

---

Common Pitfalls: Recognition Humor

Purpose: Point out mistakes they've ALREADY made

Tone: Short, sharp, true. Should make them wince in recognition.

Good:

• "Forgetting annual license renewals (they spike a single month)"
• "Not modeling headcount ramps accurately (use hiring pipeline data)"
• "Mixing accrual P&L with cash flow" ← Implies "yes, we know you've done this"

Pattern: State the mistake + why it matters or what it reveals

Avoid:

• Judgment: "Only amateurs forget renewals"
• Long tangents: [3 paragraphs on why renewals are hard]
• Fake stakes: "This could DESTROY your forecast!"

Frequency: 2-3 per post, embedded in relevant steps (not lumped into one section)

---

Diagnostic Moments: Make Them See Themselves

Purpose: "Oh shit, that's us" moments

Good:

• "If your forecast shows DSO trending to 60 days (vs. target of 30), you can flag this to Sales Ops..."
• "When the CFO asks, 'Why did we miss the forecast?' and you have no assumption sheet"
• "The board deck says $1.8M cash at quarter-end. Your bank says $1.2M."

Pattern: Describe a situation that reveals dysfunction + tie to the fix

Avoid:

• Soft language: "Sometimes forecasts can be inaccurate"
• Blame: "This is why your finance team is incompetent"
• Hypotheticals: "Imagine if you could never forecast accurately—terrible, right?"

---

Closing: Contrarian Insight, Not Punchline

Purpose: Leave them sharper than they arrived

Good:

• "Running out of cash is a choice, not a surprise" ← Reframes agency
• "Better execution = lower IRI = lower WACC = higher valuation" ← Shows the chain
• "This is Law 7 in action" ← Connects to bigger system

Avoid:

• Inspirational: "Now go forth and forecast with confidence!"
• Jokey: "May your cash flows be ever in your favor"
• Upsell-y: "Contact us to learn more about our forecasting services"

Pattern: One sharp truth that reframes the task's importance

---

Voice Guidelines

Direct, Not Diplomatic:

• ✅ "This will fail if you mix accrual and cash accounting"
• ❌ "Stakeholders should carefully consider the distinction between accrual and cash methodologies"

Contrarian, Not Consensus:

• ✅ "Most best practices are aspirational fiction"
• ❌ "Following industry best practices is recommended"

Precise, Not Vague:

• ✅ "Reducing DSO from 60 to 45 days releases $250K for a $5M ARR company"
• ❌ "Improving collections can significantly impact cash position"

Technical but Accessible:

• ✅ "Cash Collections (Month N) = New Bookings (Month N-1) × (1 - DSO/30)"
• ❌ "We utilize a sophisticated temporal mapping algorithm for liquidity projection"

---

Wit Placement Map

Section	Tone	Wit Level	Examples
Hook	Contrarian	Medium	"Most CFOs treat X as Y"
Task Overview	Clinical	Zero	Just the facts: ID, level, domain
Step-by-Step	Precise	Zero	Formulas, checklists, examples
Common Pitfalls	Sharp	Low	"Forgetting renewals is how you explain..."
KPI Impact	Analytical	Zero	Formulas, owners, frequencies
ValuationOps Connection	Insightful	Low	"Better execution = lower WACC"
FAQ	Helpful	Zero	Answer the question directly

---

The F-001 Standard

The F-001 cash flow forecast post exemplifies this balance:

• Hook: "Most CFOs treat cash flow forecasting as a compliance exercise" ← Contrarian
• Stakes: "The difference between strategic optionality and emergency financing at punitive terms" ← Sharp
• Execution: Clinical step-by-step with formulas
• Pitfalls: "Mixing accrual P&L with cash flow" ← Recognition moment
• Closing: "Running out of cash is a choice, not a surprise" ← Reframes agency

Use F-001 as the tone template for all task posts.

---

Anti-Patterns (What NOT to Do)

❌ Forced callbacks: "As we discussed in the intro..." (just make your point)
❌ Dad jokes: "Why did the CFO cross the road? To reconcile the other side!"
❌ Corporate speak: "Leverage synergistic opportunities to optimize cash velocity"
❌ Jargon stacking: "Utilize EBITDA optimization strategies for liquidity enhancement"
❌ Try-hard edginess: "CFOs are basically astrologers with Excel"
❌ Fake stakes: "This ONE WEIRD TRICK will REVOLUTIONIZE your cash forecast!"

---

Style Rules (Unchanged)

• Use H2 (##) for major sections, H3 (###) for subsections
• Keep paragraphs short (2-4 sentences)
• Use callouts (::: tip, ::: warning) for key insights
• Include checklists where applicable
• Front-load information (answer the question in the first sentence)

---

3. IMAGE GENERATION

Use the GFE master prompt formula from .agent/image-generation-master-prompt.md:

Base Prompt:

Minimalist 3D relief illustration on an off-white background. Subtle paper/porcelain embossing with soft shadows and beveled edges. Accent color: muted teal (#1AA8A0). Subject: [TASK VISUAL METAPHOR]. Composition: centered, balanced, plenty of negative space, shallow depth, gentle gradients, faint ripple/contour lines behind the subject. Typography (optional): clean sans, dark slate, 2-4 words. Lighting: soft top-front, no harsh contrast.

Subject Formula:

• For forecasting tasks: "12-month timeline with flowing currency symbols"
• For analysis tasks: "Data layers converging into single KPI dial"
• For reporting tasks: "Stacked financial reports with highlighted metrics"

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

---

4. SEO & AEO OPTIMIZATION

Target Keywords

• Primary: "[Task title]" (e.g., "monthly cash flow forecast")
• Secondary: "[Domain] Level [N] task", "[Category] guide"
• Long-tail: "how to [task title] for [valuation purpose]"

Answer Engine Optimization

Structured Data (JSON-LD)

Already included in frontmatter (application/ld+json script tag). This enables:

• Rich results in Google Search (step-by-step cards)
• Voice assistant answers ("How do I build a cash flow forecast?")
• AI training data for ChatGPT, Claude, Perplexity

FAQ Section (10-13 Questions)

Include at least 10 FAQ items targeting common search queries and "People Also Ask" patterns.

Required Questions (every task post):

1. "What level do I need to be to do this task?"
2. "Which KPIs does this task affect?"
3. "How does this task connect to valuation?"
4. "What if I don't have [historical data/tools/access]?"

Domain-Specific Questions (Finance example): 5. "Should I include [technical detail] in [task output]?" (e.g., SBC in cash flow) 6. "How long does it take to [do this task]?" 7. "What tools do I need?" 8. "Can I automate this with AI?" 9. "What's the difference between [this task] and [related concept]?" 10. "How do I handle [edge case/common variation]?" 11. "What if my [output] is always wrong?" 12. "Should I include [one-time events/exceptions]?" 13. "How do I present this to [stakeholder]?"

Answer Format:

**Q: [Question in natural language]**  
A: [Direct answer in first sentence]. [Supporting detail]. [Example if helpful].

Example:

**Q: Can I automate this with AI?**  
A: Partially. AI can pull data from systems and flag anomalies, but you still need human judgment for assumptions (e.g., "Will this customer pay on time?"). The reconciliation and CFO review can't be automated.

AEO Best Practices:

• Answer the question in the FIRST sentence
• Use natural language (how people actually search)
• Include units/specifics ("2-3 hours" not "not long")
• Front-load the value ("No—SBC is a non-cash expense" not "Well, it depends...")

---

5. FINAL CHECKLIST

Before publishing:

• [ ] Task schema data accurately extracted
• [ ] All KPI links resolve and show correct details
• [ ] Process linkage is correct (if applicable)
• [ ] OKR reverse lookup is accurate
• [ ] ValuationOps layer mapped correctly
• [ ] Canon law references are valid (Laws 1-10 only)
• [ ] Hero image generated and displays correctly
• [ ] TraceabilityChain sidebar is complete
• [ ] Frontmatter traceability object is populated
• [ ] All internal links tested locally
• [ ] SEO metadata complete (title, description, OG tags)

---

End of Template