Plan With Code, Not Prose: pstack Pt. 2
Part two of poteto's pstack guide covers the front half of the agent workflow: research, planning, prototyping, and architecture. She argues agents mostly fail for two reasons — under-specified intent and missing context — so she has the agent restate a reported problem in its own words before touching code, then uses /how, /why, /recall, and /teach to rebuild runtime mechanics and historical motivation from git history, PR comments, Linear, Slack, Datadog, and Sentry. Planning happens in code rather than prose: README-driven development, a tutorial written before the API, throwaway prototypes driven by /control-app with screenshots and timing measurements, and /architect, which spins up parallel design candidates across model families and has a different model cross-judge them. Escape hatches like any, forced casts, or the same workaround at unrelated call sites count as proof the design is wrong. Aimed at engineers already shipping agent-written code to production.