Robert's Thinking Framework FAQs

Name: Robert's Thinking Framework
Author: ArcBlock

Question 1

What is the core purpose of the What Robert Thinks skill?

Accepted Answer

It is designed to evaluate technical proposals, code, and product directions against a high-standard engineering philosophy that prioritizes long-term correctness over short-term gains.

Question 2

What does 'Anchor Points' mean in engineering documentation?

Accepted Answer

Anchor points are specific, verifiable details like file paths, exact priorities, and risk assessments that make a document actionable rather than a summary of empty methodology.

Question 3

What is the Readback Principle mentioned in the skill?

Accepted Answer

It is a communication discipline where engineers repeat requirements back to stakeholders to confirm absolute understanding and prevent building the wrong solution.

Question 4

Is this skill specific to ArcBlock developers?

Accepted Answer

While it references ArcBlock's AFS/AINE architecture, the core principles of precision, simplicity, and discipline are applicable to any high-stakes software engineering project.

Question 5

How does this skill handle technical complexity?

Accepted Answer

It treats complexity as a 'smell,' encouraging developers to redesign systems that are hard to explain or maintain, following the KISS (Keep It Simple, Stupid) principle.

Robert's Thinking Framework

Key Features

Use Cases

Robert's Thinking Framework

Key Features

Use Cases