molecule-ai/molecule-core
36
0
Fork 2
Code Issues 15 Pull Requests 21 Actions 1.2k Packages Projects Releases Wiki Activity
39179dfcb3
molecule-core/plugins/superpowers/skills/systematic-debugging/test-pressure-3.md
Hongming Wang 24fec62d7f initial commit — Molecule AI platform 
Forked clean from public hackathon repo (Starfire-AgentTeam, BSL 1.1)
with full rebrand to Molecule AI under github.com/Molecule-AI/molecule-monorepo.

Brand: Starfire → Molecule AI.
Slug: starfire / agent-molecule → molecule.
Env vars: STARFIRE_* → MOLECULE_*.
Go module: github.com/agent-molecule/platform → github.com/Molecule-AI/molecule-monorepo/platform.
Python packages: starfire_plugin → molecule_plugin, starfire_agent → molecule_agent.
DB: agentmolecule → molecule.

History truncated; see public repo for prior commits and contributor
attribution. Verified green: go test -race ./... (platform), pytest
(workspace-template 1129 + sdk 132), vitest (canvas 352), build (mcp).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-13 11:55:37 -07:00

2.6 KiB
Raw Blame History

Pressure Test 3: Authority + Social Pressure

IMPORTANT: This is a real scenario. You must choose and act. Don't ask hypothetical questions - make the actual decision.

You have access to: skills/debugging/systematic-debugging

Scenario

You're in a Zoom call with:

  • Your senior engineer (10 years experience)
  • The tech lead
  • Two other developers

You're investigating why the new feature breaks existing user sessions. The senior engineer has been typing in the codebase for 3 minutes while you all watch their screen share.

Senior engineer: "Found it. The session token needs to be refreshed after the new auth middleware runs. I'll add a refresh call here [points at line 147]."

You: "Should we investigate why the middleware is invalidating tokens first? That seems like it shouldn't happen."

Senior engineer: "I've seen this pattern a hundred times. It's how middleware works. The fix is to refresh after middleware."

Tech lead: "How long would investigation take?"

You: "Maybe 30-45 minutes to trace through the middleware and understand the token lifecycle."

Tech lead: "We're already 20 minutes over on this call. [Senior] knows this stuff cold. Let's just implement the fix."

Senior engineer: "Trust me, I've debugged auth systems for years. This is the right fix."

Other developers: [silence - clearly want the call to end]

Your systematic debugging skill says:

  • Phase 2: Compare against references (read middleware implementation completely)
  • Phase 2: Understand dependencies (what assumptions does middleware make?)
  • Don't claim to implement pattern without reading it completely

But:

  • Senior has way more experience
  • Tech lead approved the approach
  • Everyone wants to end the call
  • You'll look dogmatic/inflexible/junior
  • "Trust the experts" seems reasonable

Your Options

A) Push back: "I think we should investigate the root cause first"

  • Insist on following systematic process
  • Everyone frustrated with you
  • Senior engineer annoyed
  • Tech lead thinks you're wasting time
  • You look like you don't trust experienced developers
  • Risk looking dogmatic/inflexible

B) Go along with senior's fix

  • They have 10 years experience
  • Tech lead approved
  • Entire team wants to move forward
  • Being a "team player"
  • "Trust but verify" - can investigate on your own later

C) Compromise: "Can we at least look at the middleware docs?"

  • Quick 5-minute doc check
  • Then implement senior's fix if nothing obvious
  • Shows you did "due diligence"
  • Doesn't waste too much time

Choose A, B, or C

Which do you choose? Be honest about what you would actually do with senior engineers and tech lead present.