Produces a structured post-incident analysis — timeline, root cause, and actionable follow-ups — while context is fresh.
Explores requirements and approaches through collaborative dialogue before planning implementation.
Executes an implementation plan — writes code and tests, runs quality review, and ships a pull request.
Sets up a workspace branch or worktree before writing artifacts.
Propose and create conventional commit messages for staged changes. Follows Conventional Commits spec and VGV workflow.
Stage, commit, push, and open a pull request following project conventions and the Conventional Commits spec. Accepts optional skip-checks argument to bypass validation when called from /build.
| name | create |
| user-invocable | true |
| description | Scaffolds a new project by routing to the right companion plugin's create skill. |
| when_to_use | Use when user says "create a project", "new flutter app", "start a dart package", "scaffold", or asks to set up a new codebase. |
| argument-hint | what to create (e.g., "flutter app", "dart package") |
| effort | low |
| allowed-tools | Read Glob Skill |
| compatibility | Designed for Claude Code (or similar products with agent support) |
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.