product engineering

a toolkit of skills, agents, workflows, resources, and apps for building products.

philosophy

building a product is a context-decision loop. context informs a decision, and that decision generates new context for the next one. the loop never stops turning.

the loop is powered by work, which generates artifacts — research, conversations, designs, tradeoffs, documentation, feedback. they might live across different tools, different teams, and different moments. when you look for the full picture behind a decision, you find fragments. not because anyone organized them wrong, but because there just wasn't something to connect them. that means you either spend time rebuilding context that already existed, or move forward without it.

the loop keeps turning, but each turn has less to work with. this is context degradation. the further you get from a decision, the harder it is to trace why it was made. eventually you stop looking and start assuming.

product engineering exists to reduce that degradation — a way to organize work that aims to keep context connected and findable, so the next decision builds on the last, not from scratch.

the build loop

the build loop is a way to organize work — diverging and converging steps that move from open exploration to focused execution, then package everything for the next turn.

explore

diverge. go wide across the problem space. play with possibilities and discover what you don't know.

shape

converge. mold what you explored into something concrete enough to build. narrow from idea to plan.

ship

execute. execute with the living context of why this matters, who it's for, what success looks like, and how to do it.

compound

package. close the loop. package what you shipped, learned, and heard so the next cycle starts with more context, not less. this is compounding in motion.

who this is for

builders who blur the lines between product, design, and engineering — and want a composable system focused on reducing context degradation.