tony-adamson
- 12 skills
- 0 followers
- last month last updated
- ▌ Debug 2 · tony-adamson bundleUse when explicitly asked for $debug, or when a bug survived the first fix, is intermittent, or is a performance regression: build a feedback loop that goes red on the bug, minimise, rank falsifiable hypotheses, instrument, fix with a regression test at a correct seam, clean up. Do not use for a first-read error that the stack trace already explains.
- ▌ Planf3 2 · tony-adamson bundleUse when explicitly asked for $planf3 to create, update, or build a minimal Markdown implementation plan from SOLUTION.md or a concrete approved task. Do not use for solution design or speculative architecture.
- ▌ Ops Review 2 · tony-adamson bundleUse when explicitly asked for $ops-review to review an implemented change for silent operational failures: missing timeouts, unbounded resources, connection leaks, non-idempotent retries, slow-dependency degradation. Read-only findings report; does not fix code and does not replace load testing.
- ▌ Scope Review 2 · tony-adamson bundleUse when explicitly asked for $scope-review to review a diff for excess scope before a PR: additions without a forcing requirement, foreign patterns, indirection layers, duplication, files outside the task frame. Read-only findings report; does not fix code.
- ▌ Solution Design 2 · tony-adamson bundleUse when explicitly asked for $solution-design to create SOLUTION.md for one concrete software change before implementation planning. Produces a minimal evidence-based design; does not write code or create an implementation plan.
- ▌ Codebase Analysis 2 · tony-adamson bundleUse when explicitly asked for $codebase-analysis to create or fully update CURRENT_STATE.md with evidence for the current repository or focused area. Do not use for casual code questions, reviews, implementation, debugging, solution design, or planning.
- ▌ Debug · tony-adamsonDisciplined diagnosis loop for hard bugs, flaky failures and performance regressions: build a feedback loop that goes red on this bug → minimise → rank hypotheses → instrument → fix with a regression test → clean up. Use when the user says debug/diagnose, or reports something broken, throwing, failing intermittently or slow, and the first read of the error did not fix it.
- ▌ Planf3 · tony-adamson bundleCreates or executes a minimal Markdown implementation plan based on SOLUTION.md or an explicit request. Use only when the user explicitly asks: planning or Build Plan. No presentation artifacts and no future-proof architecture.
- ▌ Ops Review · tony-adamson bundleReviews an implemented change for silent operational failures: missing timeouts, unbounded resources, connection leaks, non-idempotent retries, slow-dependency degradation. Read-only, findings only, no fixes. Use only when the user explicitly asks to run ops-review.
- ▌ Scope Review · tony-adamsonРевью обоснованности diff перед PR: каждое добавление вызвано текущим требованием, код мимикрирует под локальные паттерны, нет прослоек и дублирования, diff гигиеничен. Только находки, без правок. Запускать только по явной просьбе пользователя.
- ▌ Solution Design · tony-adamson bundleCreates SOLUTION.md for one concrete task: the minimal sufficient solution, grounded in the requirements, CURRENT_STATE.md, and live code. Use only when the user explicitly asks to run solution-design. Does not write code and does not create an implementation plan.
- ▌ Codebase Analysis · tony-adamson bundleCreates CURRENT_STATE.md: an evidence-backed description of the current state of the repository. Use only when the user explicitly asks to run codebase-analysis. Does not design a solution, write code, or produce an implementation plan.