Twitter/X

Author @tomcrawshaw01 asserts senior engineers don't prompt better by default but…

2026-08-05 · 16:11 UTC ·@tomcrawshaw01 ·1 min read

Brief

Tom Crawshaw (@tomcrawshaw01) argues senior engineers' prompting advantage is actually five repeatable practices—brainstorming, writing detailed plans, fresh subagents per task, verification gates, and root-cause debugging—enforced by a free one-line plugin (/plugin install superpowers@claude-plugins-official). He details each enforcement rule and asks who else is using the plugin (posted 2026-08-05).

Why it matters

Author @tomcrawshaw01 asserts senior engineers don't prompt better by default but have 'installed' five reproducible skills: Brainstorming, Writing plans, Subagent-driven development, Verification before completion, and Systematic debugging.

Key details

  • Each skill has enforcement rules: Brainstorming runs before anything exists and interviews the user; Writing plans outputs a file detailed enough for someone with zero context; Subagent-driven development spawns a fresh agent per task and reviews after each step; Verification requires running checks and showing output before marking done; Systematic debugging must find root cause and treating error-message edits as failures.
  • All five skills come from a free plugin installed with one line: /plugin install superpowers@claude-plugins-official — post published 2026-08-05 and the author asks who else is using it.
Source evidence

Senior engineers don't prompt better than you.

They installed these 5 skills.

  1. Brainstorming. Runs before anything exists. It refuses to build until it's interviewed you and you've signed off on what you actually want.

  2. Writing plans. Still nothing built. It takes what you agreed and writes it to a file, in enough detail that someone with zero context could follow it.

  3. Subagent driven development. Now it builds. Fresh agent per task, reviewed after each one, so it never gets halfway through and forgets what it's doing.

  4. Verification before completion. The gate at the end. It isn't allowed to tell you it's done until it's run the check and shown you the output.

  5. Systematic debugging. This one only fires when something's broken. It has to find the actual cause before it's allowed to change anything, and patching the error message counts as a failure.

All five come from one free plugin, and it's one line to install:

/plugin install superpowers@claude-plugins-official

Who else is using the for their builds?