Skip to content

/competitive-report-structure

Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Use when presenting

From plugin
ecc
293k200 skills71 agents113 commands1 MCP

Claude Code

$ npx -y skills add affaan-m/ECC --skill competitive-report-structure --agent claude-code

SKILL.md

competitive-report-structure.SKILL.md
name: competitive-report-structure
description: Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Use when presenting competitive findings to leadership or a board, writing a competitive landscape report, or as the final step of the competitive analysis pipeline.

Competitive Report Structure

Use this skill to assemble scored competitor cards into a decision-grade report. The report must answer three questions for the client: **who do we compete with, how do we compete, and where is our defensible white-space?** Every section earns its place by moving toward those answers — cut anything that doesn't.

When to Activate

  • All competitor profile cards from benchmark-methodology are complete and ready to assemble.
  • Need to present competitive findings to a founder, leadership team, or board.
  • The report must drive decisions (who to compete with, how, where the moat is) — not just document the landscape.
  • Preparing a client deliverable that must be auditable and defensible.

Client positioning brief (establish first)

Before assembling the report, establish the client's positioning brief. It supplies:

  • **Strategic tension** — the paired axes (e.g., memorability × hireability)

that define the client's target white-space. All maps and synthesis resolve back to this tension.

  • **Brand balance** — the intended proportional mix of the client's strategic

emphases (e.g., 60% strategy/evidence, 25% distinctiveness, 15% craft). Every recommendation must be checked against this balance; flag any that would shift it.

  • **Differentiator** — the framing principle for the executive summary and

white-space section.

  • **Target quadrant** — where the client intends to sit in the tension map;

confirming whether that quadrant is genuinely open is the report's central empirical question.

Framing principle

The whole report is organized around the client's strategic tension and recommendations resolve back to the client's deliberate brand balance. Recommendations that would break that balance must be flagged against it explicitly — "this move shifts the balance from X/Y/Z toward A/B/C; confirm intent."

Report sections

1. Executive summary

3–5 takeaways, decision-first. State the most important findings in plain language: where the client is strong, where it's exposed, who occupies its target white-space, and the top 2–3 moves. Written so a founder/PM reads only this and knows what to do. No methodology here.

2. Market landscape & category framing

Define the category and map it. Use a **multi-axis map** — at minimum a 2×2 (e.g., *brand-led <-> capability-led* × *boutique <-> enterprise-scale*), and ideally the **client's tension plot** from `benchmark-methodology` as the headline map. Place every profiled competitor and the client. The map should make the client's intended position visually obvious and show how crowded (or empty) it is.

3. Competitor tiers

Organize the set into **Direct / Adjacent / Aspirational** (from `competitive-platform-analysis`). One short paragraph per tier explaining who's in it and why it matters to the client. This sets reader expectations before the detail.

4. Benchmarking matrix

The full **competitors × dimensions** table — the quantitative spine. Rows = competitors (grouped by tier), columns = the nine benchmark dimensions (note: dimension 9 — strategic tension — has two poles (e.g., Memorability and Hireability for a brand-studio client; substitute the client's own paired axes); represent them as two separate sub-columns rather than averaging them). Include the client's own honest self-assessment as a row for contrast. Use a **heatmap** (color or symbol scale) so strength/weakness patterns are scannable. Do **not** add a blended total column — report dimensions separately (per the bias controls). Call out the columns where the client leads and where it trails.

5. Deep dives

3–5 most instructive competitors in narrative form (from their profile cards). Choose for instruction, not ranking: the best exemplar of the target tension (high on both poles), the cautionary "one pole only" case, the "competent but forgettable" archetype the client defines against, plus any direct threat. Each deep dive: what they do, what the client should learn, what the client should avoid.

6. White-space & threats

The strategic heart. Two parts:

  • **White-space:** the position the client can own that rivals don't — argued

from the maps and matrix, not asserted. Confirm whether the target quadrant (from the positioning brief) is genuinely open.

  • **Threats:** who/what pressures the client — a rival closing the gap,

substitutes (no-code/AI tools, in-house teams, generalist freelancers), or category shifts. Be honest about the client's own risks (e.g., a bold identity reading as un-serious to risk-averse buyers).

7. Strategic recommendations

Concrete, prioritized moves: who the client competes with, how it differentiates, and where to invest (offer packaging, evidence/case studies, thought leadership, brand sharpening). **Tie every recommendation back to the brand balance from the positioning brief** and flag any that would shift it. Sequence by impact × effort.

8. Sources / methodology appendix

The dimensions, weights, rubrics, the scoped set with tiers, source links per competitor, and verification notes (asserted vs proven). This is what makes the report auditable and defensible — carry the adversarial citation discipline through.

How to present data

  • **2×2 / positioning maps** — for landscape and the tension plot. Lead with

these; they carry the argument faster than prose.

  • **Heatmap matrix** — for the competitors × dimensions comparison (section 4).
  • **Profile cards** — the source unit feeding de
Read more
@affaan-m
Ships withecc

Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills

293k200 skills71 agents1 MCP
Get the whole plugin, auto-invoked

Stars on GitHub

Momentum

stars in total
293.5k
Star history of affaan-m/ECC on GitHub, a chart by star-history.com

Other skills on ecc.

accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

@affaan-m@affaan-mInstall Skill
agent-architecture-audit
Auto-invoked

agent-architecture-aud…

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution,…

@affaan-m@affaan-mInstall Skill
agent-eval
Auto-invoked

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and…

@affaan-m@affaan-mInstall Skill
agent-harness-construction
Auto-invoked

agent-harness-construc…

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when…

@affaan-m@affaan-mInstall Skill
agent-introspection-debugging
Auto-invoked

agent-introspection-de…

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.…

@affaan-m@affaan-mInstall Skill
agent-security-hardening
Auto-invoked

agent-security-hardeni…

Security hardening guidance for AI agent frameworks that process untrusted content, invoke tools, write workspace files, manage…

@affaan-m@affaan-mInstall Skill

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills10d309k
@mattpocock@mattpocockInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react1d252k
@facebook@facebookInstall Skill
act-on-feedback

act-on-feedback

Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit…

vscode1d195k
@microsoft@microsoftInstall Skill

Questions about competitive-report-structure.

Which coding agents can use competitive-report-structure?
competitive-report-structure installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.