wsp-new-feature
Create a new wsp workspace for a feature
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Create a new wsp workspace for a feature
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Manage multi-repo workspaces with wsp
Cut a wsp release (dry-run, execute, verify)
Report a wsp issue on GitHub with full diagnostic context
Verify all built-in skills are registered in check_claude_dir managed sets
| name | wsp-new-feature |
| description | Create a new wsp workspace for a feature |
| user_invocable | true |
Create a new wsp workspace for working on a feature across one or more repositories.
<name> (required) — the workspace name (typically a feature branch name like jganoff/my-feature)Check if the current workspace was created from a template:
wsp st --json
Look at the created_from field in the JSON output. If it has a value, offer to use the same template. Otherwise, list available templates:
wsp template ls --json
Present the templates to the user and let them pick one. If no template fits, ask the user which repos to include.
If using a template:
wsp new <name> -t <template> --json
If using ad-hoc repos:
wsp new <name> <repo1> <repo2> ... --json
Parse the JSON output and report:
Tell the user they can cd into the workspace path to start working, or use wsp cd <name> if they have the shell integration set up.
--json when calling wsp programmatically. JSON output goes to stdout; progress messages go to stderr.wsp new fails because mirrors are missing, suggest running wsp registry add <repo> first to set up the bare clones.