agentmods.dev

gaps

A command for finding missing or underdeveloped product features by comparing a product with competitors and user requests.

In plain words
What is it for?
Use it to identify competitor gaps, spot trends, review customer-requested features, and match findings against existing GitHub issues.
Why use it?
It brings product information, competitor research, existing requests, and GitHub issues together so gaps are not overlooked or duplicated.

Command

483 1mo ago A scan 7 tokens original MIT
View the source file ooiyeefei/ccc
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/ooiyeefei/ccc/gaps
Clone the repo
git clone --depth 1 https://github.com/ooiyeefei/ccc
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 485 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00007 $0.00485
Opus 5 $0.00003 $0.00243
Sonnet 5 $0.00001 $0.00097
Haiku 4.5 $0.00001 $0.00049

Measured 3d ago against content hash edc4e9dc682f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gaps scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/product-management/commands/gaps.md · 61 lines

What it actually says

Gap Analysis

Identify product gaps and score with WINNING filter.

Prerequisites Check

  1. Verify .pm/product/inventory.md exists

    • If missing: "Run /pm:analyze first to create product inventory."

  2. Verify .pm/competitors/*.md files exist

    • If missing: "Run /pm:landscape first to research competitors."

  3. Check staleness in .pm/cache/last-updated.json

    • If competitor data >30 days old: Prompt to refresh first

Process

Use the gap-analyst agent for systematic analysis:

  1. Sync with GitHub Issues for deduplication:

    gh issue list --label "pm:feature-request" --json number,title,body,labels --limit 100

    Update .pm/requests/ with current issues.

  2. Load Context

    • Read .pm/product/inventory.md
    • Read all .pm/competitors/*.md
    • Read .pm/requests/*.md (existing issues)

  3. Identify ALL Gaps

    • Features competitors have that we don't
    • Features multiple competitors are building (trends)
    • Features from user reviews/requests

  4. Deduplication Check For each gap, fuzzy match against existing issues:

    • 80% match → Mark EXISTING (show linked issue)

    • 50-80% → Mark SIMILAR (warn user)
    • <50% → Mark NEW (proceed with scoring)

  5. WINNING Filter Scoring (hybrid):

    • Claude suggests: Pain Intensity, Market Timing
    • Ask user to score: Execution, Fit, Revenue, Moat

  6. Recommendations

    • 40-60: FILE (high conviction)
    • 25-39: WAIT (monitor)
    • 0-24: SKIP

  7. Save Analysis

    • Save to .pm/gaps/[YYYY-MM-DD]-analysis.md
    • Update .pm/cache/last-updated.json

Reference references/winning-filter.md in the product-management skill for scoring criteria.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 61 lines · 7 tokens per session scan A edc4e9dc682f

Subscribe to this mod's changes

gaps is a command published in the GitHub repository ooiyeefei/ccc (483 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 485 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Marketing and SEOPlanning
Related

Other commands, from other repositories

git

Git operations with intelligent commit messages and workflow optimization.

SuperClaude-Org/SuperClaude_Framework · 11 tokens

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens