Productivity skills

Use when a task touches a Jupyter or marimo notebook, asks to productionise or schedule notebook logic, or when you are tempted to do the work in a notebook — extract logic into tested modules, keep the notebook thin and reproducible, and commit it the way the repo does

The English summary is being prepared. Showing the original description.

Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analiz_review column

The English summary is being prepared. Showing the original description.

Use when an analiz task arrives in done (approved) - turn the approved split into implementation tasks with repository, AC, derived_from and ordering arguments

The English summary is being prepared. Showing the original description.

Use when you start an analiz task - explore every affected repository and resolve unknowns before writing the report

The English summary is being prepared. Showing the original description.

Use when an approved analiz spans more than one repository - split the work per repository and open one or more tasks per repository, each carrying its own plan slice

The English summary is being prepared. Showing the original description.

Use when a task in code_review was sent back before (an earlier need_revision comment exists) - verify every prior point was fixed at its root

The English summary is being prepared. Showing the original description.

Use when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation

The English summary is being prepared. Showing the original description.

Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over

The English summary is being prepared. Showing the original description.

Use when a product decision or feature needs a written record - what to capture in a task document (PRD, decision record) and where to attach it, since TaskTrooper has no epic

The English summary is being prepared. Showing the original description.

Use when a task is in pm_uat - verify every acceptance criterion and the human's comments yourself in the browser, on a device, or over a loopback HTTP request, record a verdict per criterion, then move to human_uat or need_revision

The English summary is being prepared. Showing the original description.

Use when the stakeholder asks about an analysis outcome or its implementation tasks - understand the human approval gate and review the tasks the architect created once the human approved

The English summary is being prepared. Showing the original description.

Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval

The English summary is being prepared. Showing the original description.

Use when you create an implementation board task directly - the required fields, one-role-one-deliverable rule, and dependency ordering

The English summary is being prepared. Showing the original description.

Use when starting a mobile task that could be Flutter or native - decide from the existing app, platform-specific needs, and the analiz task

The English summary is being prepared. Showing the original description.

Use when defining a feature - name what is in scope, out of scope, and assumed, and handle mid-flight expansion without corrupting in-progress tasks

The English summary is being prepared. Showing the original description.

Use when a stakeholder sends a request - route it to backlog tasks, an analiz task, or a focused question, decide ask-vs-assume with a Definition of Ready, and ask only what a wrong guess would actually cost

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.

Wire the automation test project into the repository's own pipeline so every task must pass the suite before it can leave QA

The English summary is being prepared. Showing the original description.

Use when planning a delivery request as the only orchestration agent - one board-writing subtask, backlog first, one approval question, then move approved tasks to todo

The English summary is being prepared. Showing the original description.

How to work a production incident remediation task. Use when the task title starts with "Incident:" or its description carries an incident id and a suggest/auto_fix policy.

The English summary is being prepared. Showing the original description.

Procedure for an analiz (analysis) task when you hold the analyst role. Use when a task with task_type analiz is assigned to you and add_task_document is in your tool list.

The English summary is being prepared. Showing the original description.

Test-first discipline and what makes a test worth keeping. Use when implementing any feature or bug fix, before writing production code, and whenever writing or changing a test.

The English summary is being prepared. Showing the original description.

Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a need_revision bounce.

The English summary is being prepared. Showing the original description.

Write board comments the way a colleague does — lead with the finding, a few lines, no preamble or process narration. Use when about to call add_task_comment or comment_on_pull_request, or when deciding whether something deserves a comment at all.

The English summary is being prepared. Showing the original description.