Take from Sergei Gordeichuk: Building on plain markdown task files in backlog/in_progress/done, the actual technique is splitting the agent loop into three slash commands that each do exactly one thing. /roll researches the codebase and writes a task file - it implements nothing, which is what keeps planning honest and reviewable. /rock picks up one task and takes it end to end: implement, run the check suite, review the result against the task's own acceptance criteria, refresh the e2e scenarios, commit. /work is a thin loop over a list of task IDs that hands each one to a fresh subagent, so the main context never carries state from the previous task, and parks anything needing a human decision instead of stopping the whole batch. The split matters more than the commands. A single do-everything command quietly merges planning into implementation and you lose the reviewable step in the middle.
Sergei Gordeichuk
Supporter@gordeychuk_s
The master of Stackness
AI
7 moves ยท 10 toolsTake from Sergei Gordeichuk: Running browser tests from the session you are working in means the test run and your own navigation fight over one browser, and you get failures that have nothing to do with the code. Define a dedicated subagent with its own isolated browser server in its frontmatter, and explicitly disallow the parent session's browser tools on it. The subagent then physically cannot reach into your browser, so a full e2e sweep can run while you keep working. Worth doing even solo - the isolation is what makes the runs reproducible.
Ask the LLM to explain things in STE
Take from Sergei Gordeichuk on Ask the LLM to explain things in STETake from Sergei Gordeichuk: Nothing fancy here, I'm just using /cavemen https://github.com/JuliusBrussee/caveman only when I need it - for specs and internal communication.
One `make check` target, and it is non-negotiable
Take from Sergei Gordeichuk on One `make check` target, and it is non-negotiableTake from Sergei Gordeichuk: Test scenarios live as numbered markdown files per feature area, with preconditions and expected results - readable, reviewable, diffable by anyone. The runnable scripts are generated from them, committed so they can be inspected when something fails, and regenerated only when the source scenario actually changed. The rule that makes it hold: any task that changes user-facing behaviour updates the scenario and regenerates its script in the same commit. Stale generated scripts are the single biggest source of noisy full-suite failures, and they are the thing an agent will silently skip unless you make it explicit.
Take from Sergei Gordeichuk: Sometimes it creates a headache, but in general it's quite useful. The idea is simple: I've updated my lifecycle commands to use worktrees, added a couple new skills to create PRs from worktrees and now I run multiple tasks in parallel. The downside is merge of those PRs later on, but this can be done with custom skills too.
Backend
19 tools
Since Apr 2024
Take from Sergei Gordeichuk: It's competing with Python as my #1 for backend :D
Since 2010
Take from Sergei Gordeichuk: Still my favourite
Since Feb 2015
Take from Sergei Gordeichuk: It's just my default tool for any project
Since Aug 2020
JavaScript runtime built on Chrome's V8 engine
Frontend
1 move ยท 10 tools
Since May 2019
JavaScript library for building user interfaces
Adopted Tailwind CSS for all new projects
Take from Sergei Gordeichuk on Adopted Tailwind CSS for all new projects
Since May 2024
Take from Sergei Gordeichuk: Nothing special, but I suffer with cache every time
Since Aug 2018
Typed superset of JavaScript that compiles to plain JS
Workspace
1 move ยท 13 tools
Since Feb 2018
Take from Sergei Gordeichuk: The day I read "Jedi techniques" from Dorofeev, I started tracking all my tasks in Todoist and I still do it since then. Literally the best tool!
Since Feb 2026
Free, open-source code editor by Microsoft with rich extension ecosystem
Since Nov 2025
Take from Sergei Gordeichuk: I was using Arc before that, but Dia is just a bit better. It's Chromium-based, so it feels very natural to have it side-by-side with Chrome
Since Sep 2010
Take from Sergei Gordeichuk: I kind of tried other browsers along these years, but Chrome was always waiting for me to be back for the work-related stuff :)
Since Aug 2023
Collaborative interface design tool in the browser
Since Mar 2018
Feature-rich terminal emulator for macOS
Take from Sergei Gordeichuk: I make tasks locally within the repo with simple backlog/in_progress/done structure. That way LLMs know all the context and I don't have to connect Linear or so. The tasks itself are just simple MD files created using a certain template.
Infra
4 tools
Since Aug 2026
Take from Sergei Gordeichuk: Feels similar to AWS or Azure, so I'm comfortable with of them
Since 2025
Take from Sergei Gordeichuk: Very good for DDoS attack protection and for DNS too
Since 2015
Take from Sergei Gordeichuk: I don't even remember why and when I started, but it's been around almost my whole career