Could be (the overcomplicating part), I'm just not yet comfortable loosing the mental model of the final application. At least not in all types of tickets. Are you not seeing that?..

I focus on one side project at a time, alongside work applications

Both are giving me skillsets to excel in the other domain

I watch the subagents, push back on some choices, look at commits and glance at pull requests

If I'm attentive during spec/plan creation I sort of build this "expectation" of what the actual PR will look like, the mental model of it. Then it's somewhat easier to review. But the mental load is brutal tbh, and still not sure if it's "worth it"

our team has this link pinned in slack - very useful, normal human language used to explain!

CMS: Hugo(because it supports markdown!) Hosting: S3 bucket + CloudFront + Route53 Deployment: Upon commit, upload to s3

check it out - https://blog.envimate.com