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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

Use when you write the `plan` section of an analiz report - steps that pin files, signatures, tests and verify commands, nothing more

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

Use when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。

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

中文简介正在准备中。当前显示原文说明。