Skip to content
Agentmart
Submit a tool

continuous-improvement-loop

Run the Part 12 continuous improvement loop into a quarterly brief for leadership.

Skill by indranilbanerjee

IndexedMIT★ 909
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/indranilbanerjee-continuous-improvement-loop

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief"

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/continuous-improvement-loop

Tools it pre-approves 6

From allowed-tools in SKILL.md: the agent may use these without asking you each time.

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

What's inside

Skill name
continuous-improvement-loop
Description
Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief"
License
MIT
Allowed tools
Read, Write, Edit, Bash, Glob, Grep
Instructions
274 lines in SKILL.md · view on GitHub

Before installing

  • Pre-approves any shell command

Files (1)

  • SKILL.md

SKILL.md (first lines)

# /digital-marketing-pro:continuous-improvement-loop — Part 12 Continuous Loop

> **Script location.** If your host does not set `${CLAUDE_PLUGIN_ROOT}`, the scripts are in this plugin's `scripts/` folder, next to `skills/`. Run them with Python 3.10 or newer: `python`, or `python3` where `python` is not found (macOS, many Linux systems).

Part 12 is the continuous improvement loop that runs alongside live operations from go-live onwards. It aggregates market signals and operating signals into recommendations that feed back into the brand's product, offering, and service decisions.

## Context efficiency

Heavy skill. **Grep before Read** any referenced file, then `Read` only matched ranges with `offset` + `limit`. List the brand's workspace at `~/.claude-marketing/brands/{slug}/` (or `$CLAUDE_PLUGIN_DATA/digital-marketing-pro/brands/{slug}/` when that env var is set) before opening files. On re-invocation mid-session, skip files already in context.

This is **not a one-time activity**. It runs perpetually once Part 11 is complete, with formal output at each Quarterly Business Review (QBR) and ad-hoc output when significant signals warrant.

## Why this exists

Without an explicit feedback loop, marketing operates on assumptions made months ago. Markets shift, customers evolve, competitors move, products are refined — but if these shifts do not flow back into the strategy, the engagement silently grows stale.

Part 12 closes the loop:

- Market signals → strategy refresh
- Operating signals → tactical optimisation
- Product / offering signals → recommendations to product / business teams

## The 4 Signal Sources

### Source 1: Quarterly Business Reviews

Every quarterly review (per [reporting-cadence.md](../context-engine/reporting-cadence.md)) generates structured signals:

- KPIs vs targets (which targets were missed; which were beaten; pattern across quarters?)
- Channel-mix performance (any channel consistently outperforming or underperforming the v2 plan?)
- Audience segment performance (any segment showing different behaviour than the personas predicted?)
- Competitive shifts (any competitor moves that materially change the landscape?)
- Strategy alignment audit (is what we are executing still what the v2 strategy says we should be executing?)

### Source 2: Customer Feedback Themes

Feedback from across customer touchpoints:

- Customer service tickets (volume by topic, sentiment trend)
- ORM (Online Reputation Management) — review sites, social mentions
- Sales team conversations (objections heard repeatedly, requests not yet met)
- Customer journey friction observations (where customers drop off, where they ask for help)
- Survey / NPS responses
- Customer interviews

### Source 3: Competitive Intelligence

From the ongoing competitor monitoring (existing `/digital-marketing-pro:competitor-monitor` skill):

- Product / offering shifts at competitors
- Pricing changes
- Positioning shifts (messaging, target audience)
- New entrant emergence
- Acquisitions / partnerships changing the competitive landscape

### Source 4: Team-Discovered Patterns

Insights from execution that the team surfaces:

- Campaigns that consistently underperform — may indicate product-market mismatches
- Audiences requesting features the product does not yet offer
- Conversion friction points that recur across many campaigns
- Channel performance patterns that suggest the buyer journey has shifted

## Cadence

Part 12 is active continuously, with structured outputs:

| Cadence | Trigger | Output |
|---------|---------|--------|
| **Daily / weekly** | Automated signal capture as part of normal operations | Signals logged to `part-12-continuous-improvement/signals.jsonl` |
| **Monthly** | Monthly performance report | "Signals This Month" section in the report; logged to signals.jsonl |
| **Quarterly** | QBR | Structured Part 12 deliverable — see below |
| **Ad-hoc** | Significant signal (e.g., competitor product shift, sales team flagging recurring objection, KPI suddenly cratering) | Ad-hoc Part 12 brief produced within 1 week |

## The Quarterly Part 12 Deliverable

Each quarter, the continuous loop produces a structured deliverable for the brand business owners — not just marketing leadership.

### Structure

```markdown
---
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

From indranilbanerjee/digital-marketing-pro, MIT.

More from indranilbanerjee/digital-marketing-pro

Signals

Stars
909
Forks
146
Open issues
0
Last commit (this folder)
Oct 9, 2026 (18 days ago)
Last release
Jul 29, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from indranilbanerjee

Cite this page

continuous-improvement-loop skill. Agent Mart. https://agentmart.dev/skills/indranilbanerjee-continuous-improvement-loop (last updated 2026-10-24)