techiejd

Use when the user invokes /steelman or when a high-stakes decision is detected in context (architecture choices, technology selections, business model decisions, strategic pivots). Not for routine planning or implementation tasks.

Use when reviewing, grading, or auditing a README — before publishing a repo, after major doc changes, evaluating an OSS dependency, or when a maintainer asks "is this README good enough?". Applies a rubric across first-impression, install path, accuracy, navigation, mental model, progressive disclosure, maintenance signals, and honesty about limitations.

Use when about to start a dev server, run e2e tests, or connect to a database — proactively detects resource conflicts from other running processes and silently adapts to avoid collisions