Stephen Brouhard

How I combined the best of @poteto's pstack and @kunchenguid's Firstmate into a single runtime. Instead of letting their routers fight as separate authorities, I kept Firstmate as the outer loop for fleet orchestration and injected pstack's engineering discipline directly into the workers runtime. >Firstmate is a fleet commander (horizontal scale across Git worktrees). >pstack is an elite micro-manager (strict engineering habits and verification). Here is how I merged them into an optimized hybrid runtime: * Conditional Briefs: Worker prompts load plays just-in-time. Zero bloated prompt dumps. * Required-Read Habits: Smallest logical change, subtract code before adding, and analyze blast radius. * Context Discipline: Only map how the system is built when the change crosses into another part of it. If you skip that, write one line saying why. * Verification: "Done" requires real artifact proof (running live shell commands or generating local app verifiers). * Scaffold Isolation: Worktree checks prevent role hijack across ship, scout, and supervisor agents. I stripped out the Cursor UI dependencies for my local machine's CLI stack and skipped the expensive multi-frontier review loops. Firstmate handles the fleet isolation. The injected runtime handles the code discipline. The goal is lean, fast and deterministic. Just wired this up today, so I will be seeing how this works on my projects. html artifact- https://t.co/ArrKLwuSvk Repo links: pstack: https://t.co/v89PX4zLZC Firstmate: https://t.co/rdaEu1mJ86