What Is the Purpose of Rule 3: End with One Concrete Next Action?

Rule 3 is designed to drive the reader toward immediate execution by ensuring every interaction ends with a single, clearly-defined step that can be completed in under two minutes.

Rule 3 is a core guideline in the i-have-adhd repository, engineered to bridge the gap between advice and action for users with ADHD. As implemented in ayghri/i-have-adhd, this rule mandates that every response terminate with an explicit next move, transforming abstract recommendations into executable workflows. This architectural constraint addresses unique cognitive needs while providing deterministic output specifications for developers.

The Architectural Purpose of Rule 3

Rule 3 serves four distinct architectural functions within the skill framework. According to skills/i-have-adhd/SKILL.md (lines 59–65), this guideline ensures that every generated response terminates with a deterministic call to action.

Reduces Cognitive Overload

People with ADHD typically have limited working memory capacity. By isolating a single next step explicitly, Rule 3 prevents users from having to retain vague plans or multi-step instructions in their heads, reducing mental burden.

Eliminates Analysis Paralysis

The hardest hurdle is often simply starting. By presenting a concrete, low-effort next move, Rule 3 lowers the activation energy required to act, preventing the freeze that occurs when facing undefined or complex tasks.

Creates a Feedback Loop

When the user completes the suggested step, they receive a visible win (referenced in Rule 7), reinforcing progress and triggering dopamine release. This neurological reward encourages continued interaction and sustained workflow momentum.

Ensures Deterministic Output

From an implementation standpoint, Rule 3 gives the skill a clear, testable contract: every response must end with a single actionable statement. This makes automated verification straightforward and ensures consistent behavior across all interactions.

Implementation: Correct vs. Incorrect Usage

To satisfy Rule 3, the final line of every response must follow the pattern Next: <action>, where <action> represents a short command, file edit, or snippet executable within two minutes.

Correct Usage

Run `npm install jsonwebtoken`, then edit `src/auth.ts:42`.

Explanation of why this fixes the token verification bug…

Next: run `npm test` and paste the first failing line.

The final line Next: run npm test and paste the first failing line. constitutes the single concrete next action required by Rule 3.

Incorrect Usage

Run `npm install jsonwebtoken`, then edit `src/auth.ts:42`.

Explanation of why this fixes the token verification bug…

Let me know if you need anything else.

This closing sentence violates Rule 3 because it presents a vague prompt rather than a concrete, executable step.

Source Code Definition

Rule 3 is formally specified in the ayghri/i-have-adhd repository as one of ten governing guidelines:

• skills/i-have-adhd/SKILL.md (lines 59–65): Contains the formal definition of Rule 3 and its relationship to the surrounding rules that drive the skill’s behavior.
• README.md (lines 64–67): Summarizes the ten rules for quick reference, contextualizing Rule 3 within the overall design philosophy.

These files establish Rule 3 as a deterministic contract: every response must end with a single actionable statement, enabling automated verification and consistent user experience.

Summary

• Rule 3 mandates that every interaction end with one concrete next action to bridge the gap between advice and immediate execution.
• The rule reduces cognitive overload for users with ADHD by eliminating the need to retain vague plans in working memory.
• By lowering activation energy, Rule 3 eliminates analysis paralysis and creates immediate feedback loops that reinforce progress through dopamine-triggering wins.
• Architecturally, Rule 3 provides a deterministic, testable contract that requires every output to terminate with a Next: <action> pattern, facilitating automated quality assurance.

Frequently Asked Questions

What qualifies as a "concrete next action" under Rule 3?

A concrete next action is a specific, executable step that can be completed in under two minutes. Examples include running a terminal command, opening a specific file at a line number, or pasting a code snippet. Vague prompts like "Let me know if you need help" violate the rule because they lack deterministic execution criteria.

How does Rule 3 interact with other rules in the i-have-adhd skill?

Rule 3 works synergistically with Rule 7 (celebrate wins) to create a feedback loop: the concrete action provides an immediate task, and completion triggers a dopamine-reinforcing acknowledgment. It also supports the skill's overall goal of reducing cognitive load by ensuring users never leave the interaction without a clear path forward.

Can Rule 3 be validated automatically in generated responses?

Yes. From an implementation standpoint, Rule 3 creates a clear, testable contract. Automated validation can verify that every response terminates with the pattern Next: <action>, making it straightforward to unit test skill outputs and ensure compliance across the codebase.

Why is the two-minute time limit specified for next actions?

The two-minute constraint prevents the next action from becoming a sub-project that triggers procrastination. By keeping the step small enough to execute immediately, Rule 3 ensures the user experiences a "quick win," which is essential for maintaining dopamine levels and momentum in ADHD workflows.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}