From vgv-wingspan
Routes new project creation requests to matching companion plugins: scans recommendations, matches descriptions, verifies installation, prompts installs, invokes create skills.
npx claudepluginhub verygoodopensource/very_good_claude_code_marketplace --plugin vgv-wingspanThis skill is limited to using the following tools:
Route project creation to the right companion plugin. Wingspan does not scaffold projects itself — it discovers companion plugins from recommendation files and delegates to the matching plugin's create skill.
Scaffolds full projects from PRD + stack templates: directory structure, configs, CLAUDE.md, git repo init, GitHub push. Studies existing projects via SoloGraph, uses Context7 for library versions.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Route project creation to the right companion plugin. Wingspan does not scaffold projects itself — it discovers companion plugins from recommendation files and delegates to the matching plugin's create skill.
$ARGUMENTS
If the description above is empty:
DO NOT proceed until you have a project description.
Use Glob to find all *.json files in hooks/recommendations/ (relative to the Wingspan plugin root). Then Read each file.
Each recommendation file has this structure:
{
"plugin": "plugin-name",
"description": "What the plugin provides.",
"marketplace": "OrgName/repo-name"
}
Compare the user's project description against each recommendation's plugin name and description (case-insensitive). Pick the plugin whose description best matches the requested technology.
Check the available skills listed in the system-reminder in your conversation context for any skill prefixed with the matched plugin name (<plugin-name>:).
If no skills from that plugin are listed, the plugin is not installed. Use AskUserQuestion tool:
<plugin>' is needed but not installed. Would you like to install it?"If the user chooses to install, output the following commands and stop:
/plugin marketplace add <marketplace>
/plugin install <plugin>
Tell the user to run these commands, then re-invoke /create with the same project description. Do not proceed to Step 4.
The available skills are listed in the system-reminder in your conversation context. Look for skills prefixed with the matched plugin name (<plugin-name>:<skill-name>). Among those, find the skill whose name or description best indicates project creation (look for terms like "create", "scaffold", "new project", "generate", "init").
Invoke it using the Skill tool with its fully qualified name (e.g., my-plugin:scaffold-project), passing the user's full project description as arguments.