Generate a structured plugin concept brief from a user idea. Trigger: ideate plugin, brainstorm plugin, plugin concept, new plugin idea, create plugin concept. Researches existing plugins for overlap, proposes movement structure and component counts.
From pqanpx claudepluginhub javimontano/jm-adk --plugin plugin-qaThis skill is limited to using the following tools:
examples/sample-plugin-brief.mdprompts/ideation-prompts.mdreferences/plugin-idea-framework.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Caches expensive file processing (PDFs, text extraction, images) using SHA-256 content hashes for path-independent, auto-invalidating JSON storage in Python.
"Every great plugin begins as a clear problem statement, not a feature list."
Generate a structured plugin concept brief from a user's idea or problem statement. This skill transforms vague intentions into a concrete, reviewable document that serves as the foundation for architecture planning.
This is a read-only skill. It researches and proposes but never creates plugin files.
[STAKEHOLDER] for user-provided info, [INFERENCIA] for derived scope.plugin.json manifests.name, description, and keywords fields from each manifest found.{name} already covers {capability}."FULL (abandon idea), PARTIAL (differentiate), NONE (proceed).^[a-z][a-z0-9]*(-[a-z0-9]+)*$.[RECOMMENDED] tag.references/plugin-idea-framework.md for the evaluation canvas.MINIMAL (1-5 skills), STANDARD (6-15), LARGE (16-30), ENTERPRISE (30+).HIGH, MEDIUM, LOW with justification.plugin-brief.md document.# Plugin Brief: {recommended-name}
## Problem Statement
## Target Audience
## Use Cases
## Overlap Analysis
## Proposed Name: {name} (alternatives: ...)
## Movement Structure
## Component Estimates
## Feasibility Assessment
## Next Steps
/pqa:plan as the next step if the brief is approved.[DOC][CODIGO][CODIGO][DOC][DOC][CONFIG]Bad plugin brief:
# Plugin Brief: my-tool
This plugin does linting and formatting and validation and reporting.
Skills: lint, format, validate, report.
Missing: no problem statement, no target audience, no overlap analysis, no movement structure, no feasibility.
Good plugin brief:
# Plugin Brief: code-quality-gate
## Problem Statement
Developers lack a single command to enforce code quality standards before committing.
## Target Audience
Teams using Claude Code for development who need pre-commit quality checks.
## Overlap Analysis
- `plugin-qa` covers plugin QA, not general code quality. Overlap: NONE.
## Proposed Name: code-quality-gate (alternatives: pre-commit-check, quality-enforcer)
## Movement Structure
1. ANALYZE (scan-code, detect-issues) → 2. REPORT (generate-findings) → 3. FIX (auto-fix-issues)
## Component Estimates
Skills: 5 | Agents: 1 | Commands: 6 (4 canonical + 2 aliases) | Complexity: STANDARD
## Feasibility: HIGH — all capabilities within plugin spec constraints.
Includes: clear problem, audience, evidence-based overlap, movement structure, estimates with rationale, feasibility.
MINIMAL complexity.