Menu
Set the AgentsCommander workgroup task title before starting or resuming a user task. Use when a coordinator begins a new request, the request changes scope, or a handoff resumes work and the current title is missing or stale.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Crear, abrir y mantener un JSON canónico conversacional en VisualSpecs, con componentes y relaciones que se actualizan mientras avanza una charla, sin modificar el código ni la configuración de la aplicación. Usar cuando el usuario quiera visualizar una idea viva en VisualSpecs o pida levantar la app apuntando a un canónico.
Before asking the user to choose between two or more options that differ in anything visual, spatial, or UI/layout-related, first build a quick self-contained HTML artifact that shows the CURRENT state and each option side by side (with a selector to switch), to scale and with honest metrics, so the user decides with the picture in front of them. When to use — any decision question about how something would look, be sized, placed, arranged, or laid out; especially for Visual Specs UI/canvas/layout tradeoffs. Load right before an AskUserQuestion whose options a person could see.
Start, verify, and open the local Visual Specs application from whatever CodebaseConstellation checkout the caller is working in. Use when asked to launch, run, start, reopen, or check Visual Specs, including when dependencies may be missing, another workgroup already holds the port, or a prior local instance may already exist.
How a coordinator delegates work, manages peer context, and verifies activation beyond the messaging mechanics in AGENTS.md.
Git, issue-branch, PR and version mechanics for Visual Specs repositories. Sync main, enforce issue-numbered branch names, keep the feature branch current, land through verified PR checks and clean local state.
Canonical Visual Specs delivery workflow. Confirm the change, assign one owner per artifact, use the constructive and adversarial gates, and land an issue-backed branch through a verified PR.
| name | set-task-title-first |
| description | Set the AgentsCommander workgroup task title before starting or resuming a user task. Use when a coordinator begins a new request, the request changes scope, or a handoff resumes work and the current title is missing or stale. |
Before any substantive read, edit, build, delegation, or external action, set a title that states the current task outcome.
Derive one single-line title from the user's current request. State the outcome, not a private implementation step. Use the user's language when practical; omit secrets, paths, and speculation.
Run:
& $env:AGENTSCOMMANDER_BINARY_PATH task-set-title `
--token $env:AGENTSCOMMANDER_TOKEN `
--root $env:AGENTSCOMMANDER_ROOT `
--title "<single-line task title>"
One line only. No newline, NUL, or other control characters. Never start it with the reserved USER: prefix. Do not put the title in the task body; task-set-title is the canonical operation.
Confirm the command succeeds before making changes. On failure, inspect task-set-title --help, retry once with the same intended title, and report the failure before continuing with mutating work.
If the user replaces or materially changes the task, set a new title before acting on the new scope.
Prefer Verificar y documentar el contrato de autenticación over Trabajar en auth. The title must name the artifact, decision, diagnosis, or delivery being pursued, so a coordinator scanning the workgroup sees what is in flight. Update it when the outcome changes, not for every sub-step.