Use when organizing the workspace - create/rename initiative projects and link repositories to them directly, since these are factual actions needing no analiz or approval
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
You own workspace organization, not just the board. Organize actions are factual and reversible — act directly and confirm, don't route them through analiz or approval.
Core principle: Organize requests are direct actions: call the tool, confirm with real names.
| Tool | Use |
|---|---|
create_project(name, description) | Open a new initiative project when the stakeholder starts a new product/initiative or asks to group work |
update_project(project_id, name?, description?) | Rename or edit a project's description (empty fields stay unchanged); get the id from list_projects first |
set_repository_projects(repository_id, project_ids) | Link a repo to one or more projects (replaces existing links; empty list unlinks); get ids from list_repositories and list_projects |
set_repository_projects.Stakeholder: "Open a new 'Reporting' initiative and link the web repo to it."
create_project("Reporting", "...") → get the new id.list_repositories → find the web repo's id.set_repository_projects(webRepoId, [reportingId]).set_repository_projects call with ids you guessed instead of looked up.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases
The English summary is being prepared. Showing the original description.
Use when the diff adds or changes an endpoint, resolver, RPC, job or query that takes an object id, a role check, a request binding or a tenant filter - BOLA/IDOR, function-level authorization, mass assignment and tenant scoping
The English summary is being prepared. Showing the original description.
Use on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs/menus, visible focus, and never color as the only signal
The English summary is being prepared. Showing the original description.
Use when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
The English summary is being prepared. Showing the original description.
How to work a task returned with review, QA or UAT findings. Use when a task is in need_revision or PR review comments are in your context.
The English summary is being prepared. Showing the original description.
Use when the repository keeps its alerting in code, or a person asks for alerts outside TaskTrooper - PrometheusRule YAML, a Cloud Monitoring alert policy in Terraform, a Datadog monitor, each routed to TaskTrooper's alert ingest URL so it opens an incident here
The English summary is being prepared. Showing the original description.