Continuous Improvement Loop

What it does

When your agent uses it

• /digital-marketing-pro:continuous-improvement-loop
• Produce the quarterly improvement brief
• Aggregate this quarters signals
• We need a fast read on this competitor move

Example prompts

• “/digital-marketing-pro:continuous-improvement-loop”
• “run part 12”
• “produce the quarterly improvement brief”
• “/continuous-improvement-loop”

Requirements

• Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

1. 1Trigger: the quarter ends; QBR is being prepared
2. 2Read inputs
3. 3Aggregate signals into the four categories
4. 4Synthesise implications for strategy, channels, and product/offering
5. 5Draft recommendations for marketing, product/business, leadership
6. 6Identify v2.x update-back triggers if any
7. 7Save to quarterly-briefs/
8. 8Update LIF with quarter's verdict + recommendations
9. 9Brief: "Quarterly Improvement Brief produced. {N} signals aggregated. {N} recommendations. {N} update-back triggers identified — review…

What it can do on your machine

Read from SKILL.md and the folder at commit 3343924. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Bash
  • Glob
  • Grep

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Continuous Improvement Loop loads about 3.6k tokens when it runs. Until then it costs about 187 tokens; SKILL.md has 982 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~187

When it runs · the whole SKILL.md, loaded when a task matches

~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Read, Write, Edit, Bash, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from indranilbanerjee/digital-marketing-pro at commit 3343924, republished under its MIT licence (© indranilbanerjee). 982 words, ~3,600 tokens.

name

continuous-improvement-loop

description

Run Part 12 of the engagement methodology — the continuous improvement loop that aggregates quarterly-review, customer-feedback, competitive, and operating signals into a Quarterly Product & Offering Improvement Brief for business leadership, plus fast 1-3 page ad-hoc briefs when a significant signal lands mid-quarter. Triggers on "/digital-marketing-pro:continuous-improvement-loop", "run part 12", "produce the quarterly improvement brief", "aggregate this quarter's signals", "we need a fast read on this competitor move". Flags v2.x update-back triggers but never auto-executes them. Reads monthly reports, signals.jsonl, /digital-marketing-pro:competitor-monitor outputs, and the Living Project Instruction File.

allowed-tools

Read, Write, Edit, Bash, Glob, Grep

user-invocable

true

engagement-part

12

view-preference

both

---
document: part-12-quarterly-improvement-brief
engagement: {engagement-id}
quarter: {YYYY-Qn}
produced: {iso-timestamp}
audience: brand business leadership
---

# Quarterly Product & Offering Improvement Brief — {Quarter}

## Executive Summary

(3-5 sentences. The signals that matter most. The recommendations that follow.)

## Signal Aggregation

### Market signals
{Macro market shifts observed in the quarter}

### Customer signals
{Aggregated themes from customer feedback, ORM, sales conversations}

### Competitive signals
{Competitor moves that warrant response or reflection}

### Operating signals
{Patterns from execution — campaigns that under/outperformed; audience surprises; channel shifts}

## Implications

### For the brand strategy
{What in the v2 strategy looks confirmed by the quarter? What looks weakened? Anything that warrants v2.x update-back?}

### For the channel mix
{Any channel reweighting recommended?}

### For the product / offering
{This is the unique Part 12 contribution. What signals suggest the product or offering itself should change?}

## Recommendations

### To the marketing team
{Tactical adjustments — typically already in flight from monthly optimisation, but formalised here}

### To the product / business team
{The substantive Part 12 output — recommendations about product, offering, pricing, distribution that flow from marketing's vantage point}

### To leadership
{Strategic considerations that span functions}

## Triggers for v2.x Update-Back

(If any of the signals warrant a source-document version bump per the [update-back-rule.md](../context-engine/update-back-rule.md), list them here. The actual update-back happens via /digital-marketing-pro:engagement update-back.)

## Open Questions Raised This Quarter

(Things the data raises but cannot answer without further investigation.)

engagements/{id}/part-12-continuous-improvement/quarterly-briefs/{YYYY-Qn}-quarterly-improvement-brief.md

engagements/{id}/part-12-continuous-improvement/ad-hoc-briefs/{YYYY-MM-DD}-{slug}.md

{"timestamp":"...","source":"customer_feedback","signal":"3 sales reps reported customers asking for X integration","severity":"medium"}
{"timestamp":"...","source":"competitor_monitor","signal":"Competitor Y launched freemium tier","severity":"high"}
{"timestamp":"...","source":"performance_anomaly","signal":"LinkedIn CPL dropped 35% week over week","severity":"high","investigate":true}

User: Q2 ended last week. Produce the quarterly improvement brief.

Skill response:
1. Grep first across the Q2 monthly reports (April, May, June) for the metrics you need; targeted Read with offset+limit on the matching lines — do not bulk-Read all three reports
2. Stream signals.jsonl line-by-line for Q2 (87 signals) — use head/tail/grep, not full Read
3. Grep the competitor monitor outputs (3 significant changes); targeted Read on the matching findings
4. Grep customer feedback aggregation (47 reviews + 12 sales-rep notes) for the themes you need; targeted Read on the matches
5. Aggregate into 4 signal categories
6. Identify implications:
   - Strategy: v2 positioning held up — confirmed by 12 customer testimonials echoing the positioning language
   - Channels: LinkedIn over-performed (CPL 30% below moderate scenario); Meta under-performed (CPL 40% above)
   - Product: 8 customer signals + 4 sales-rep notes suggest Feature X is consistently asked for
7. Recommendations:
   - Marketing: shift 25% of Meta budget to LinkedIn next quarter
   - Product: prioritise Feature X for Q3 roadmap (8 named customer asks)
   - Leadership: consider a freemium tier (competitor moved here; 5 sales-rep notes about price-sensitive prospects)
8. Identify update-back triggers: Core Doc 3.4 (channel mix) needs v2.1 to reflect LinkedIn's higher allocation
9. Save quarterly-briefs/2026-Q2-quarterly-improvement-brief.md (~8 pages)
10. Brief: "Q2 Improvement Brief produced. 1 update-back trigger flagged. Run /digital-marketing-pro:engagement update-back --doc 3.4 --reason 'Q2 evidence: LinkedIn outperformed; Meta underperformed; recommend channel reweight' after leadership approval."

User: Three customers in the past two weeks have switched to a competitor that just launched a freemium tier. We need a fast read on this.

Skill response:
1. Confirm significance with engagement owner ✓
2. Read inputs: the 3 churn cases, competitor monitor on the competitor's freemium launch, last 90 days of churn data for pattern check
3. Draft brief:
   - Signal: 3 churns to Competitor Y in 14 days; pattern check shows churn rate to Y up 4x vs prior 90 days
   - Evidence: churn interview notes (2 of 3 cited price); Competitor Y launched freemium 2026-04-15
   - Implications: short-term — defensive offer for at-risk segment; long-term — pricing strategy review warranted
   - Recommended response: (1) marketing — defensive offer to current at-risk customers within 7 days; (2) product/leadership — assess freemium response within 30 days
   - Decision deadline: response plan by 2026-05-12
4. Save ad-hoc-briefs/2026-05-05-competitor-y-freemium-response.md (2 pages)
5. Distribute per approval chain

© indranilbanerjee, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/continuous-improvement-loop of indranilbanerjee/digital-marketing-pro.

Open the folder on GitHubat commit 3343924

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in indranilbanerjee/digital-marketing-pro, which our catalogue first saw on October 7, 2026.

• hashgraph-online/awesome-codex-pluginsplugins/indranilbanerjee/digital-marketing-pro/skills/continuous-improvement-loop