bevel-software/engineering-starter

YC office hours for an idea, before anything is built. Two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation and future-fit. Builder mode: design-thinking brainstorm for side projects, hackathons, learning and open source. Ends with a design doc saved to the knowledge base. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours" or "is this worth building", and before plan-ceo-review or plan-eng-review.

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, and expand or cut scope when that makes a better product — in one of four modes: scope expansion, selective expansion, hold scope, scope reduction. Then review the plan section by section: architecture, error and rescue map, security, data flow and edge cases, code quality, tests, performance, observability, rollout, trajectory and UX. Use when asked to "think bigger", "expand scope", "strategy review", "rethink this" or "is this ambitious enough", or when a plan could be thinking bigger.

Eng-manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance — walking through issues one at a time with opinionated recommendations. Use when asked to "review the architecture", "engineering review", "tech review" or "lock in the plan", and when someone has a plan or design doc and is about to start coding.

Pre-landing code review. Analyzes the diff against the base branch for SQL and data safety, race conditions, LLM trust-boundary violations, shell injection, enum completeness and other structural problems, fixes the mechanical ones and asks about the rest. Use when asked to "review this PR", "code review", "pre-landing review" or "check my diff", and when someone is about to merge.