Mehmet Akif Baysal

Use when you write or revise the analiz deliverable - the ONE self-contained HTML report (spec and plan as sections) a human reviews passage by passage

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

Use when you write the `context` and `design` sections of an analiz report - components, exact interfaces, data flow, errors, decision record, out of scope

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 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 in code_review when the diff touches input handling, auth, queries, files, outbound requests, secrets, dependencies or LLM calls, and in analysis for any new endpoint or data flow

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

Use when a task is in code_review - how to read the diff, which findings block, and the verdict move

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 diff or design adds or changes a DB migration, an endpoint or DTO, an event payload, or a shared type with consumers

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

Use when an analiz question needs the human, not the code, to decide - recording it with record_open_questions, judging blocking vs non-blocking, and resuming the report after an answer

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 you write the `plan` section of an analiz report - steps that pin files, signatures, tests and verify commands, nothing more

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 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 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 a release reaches awaiting_verdict (or you are woken for an incident) - how to read runtime logs, error groups, health and smoke evidence for the release's component and decide finish, re-check, roll back or hand to a human

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 the mobile repository has no theme tokens or component library yet (a new app, an "Apply design system" task, or a task that asks for one), before building any screen - writes the approved design system's generated files from get_design_system (files true) and builds the theme from them when there is one.

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

Use when building native iOS with SwiftUI - small composable views, observable state models, atomic components, Swift 6.2+ concurrency, and system styling over hardcoded values

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

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 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 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 ordering board tasks - set priority/blocked_by/deploy_depends_on by severity and dependency, split MoSCoW within a feature, and use RICE/ICE only for a genuine "what next" call across several features

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.

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.