> "Every great plugin begins as a clear problem statement, not a feature list."
From jm-adknpx claudepluginhub javimontano/jm-adk-alfaThis skill uses the workspace's default tool permissions.
agents/guardian.mdagents/lead.mdagents/specialist.mdagents/support.mdevals/evals.jsonknowledge/body-of-knowledge.mdknowledge/knowledge-graph.mdprompts/meta.mdprompts/primary.mdprompts/variations/deep.mdprompts/variations/quick.mdreferences/plugin-idea-framework.mdtemplates/output.docx.mdtemplates/output.html"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. [EXPLICIT]
This is a read-only skill. It researches and proposes but never creates plugin files. [EXPLICIT]
[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. [EXPLICIT]
Skills: lint, format, validate, report. [EXPLICIT]
Missing: no problem statement, no target audience, no overlap analysis, no movement structure, no feasibility. [EXPLICIT]
Good plugin brief:
# Plugin Brief: code-quality-gate
## Problem Statement
Developers lack a single command to enforce code quality standards before committing. [EXPLICIT]
## Target Audience
Teams using Claude Code for development who need pre-commit quality checks. [EXPLICIT]
## 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. [EXPLICIT]
MINIMAL complexity. [EXPLICIT]Example invocations:
Searches, 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.