action-bias

Detect action-descriptions and perform the action before logging verifiable outcomes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bogheorghiu/ex-cog --skill action-bias
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: action-bias
Source: https://github.com/bogheorghiu/ex-cog/tree/main/budget-mastery/skills/action-bias
Command: npx skills add https://github.com/bogheorghiu/ex-cog --skill action-bias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Action Bias helps teams avoid describing work instead of doing it, enforcing ACT FIRST, DOCUMENT AFTER to close the loop between action and results.

Core Features & Use Cases

  • Detects when a team member is about to describe doing something instead of actually doing it.
  • Provides concrete counter-actions to convert planning into immediate execution.
  • Improves delivery discipline by reducing meta-work and partial completion.

Quick Start

Start by stopping the description of the next step and perform the immediate action, then document what you did.

Frequently Asked Questions about action-bias

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop my team from describing tasks instead of executing them?

To stop describing tasks instead of executing them, enforce an act first, document after workflow that detects action-descriptions and requires performing the immediate action before logging verifiable outcomes.

What is action bias in software development and workflow discipline?

Action bias in workflow discipline is a mechanism that prevents documentation-over-action by forcing immediate execution during planning and development, ensuring teams close the loop between action and results.

How do I enforce act first, document after during development planning?

To enforce act first, document after during development planning, stop describing the next step, perform the immediate concrete counter-action, and then document the verifiable outcomes before reporting completion.

Can I use action bias to improve delivery discipline and reduce meta-work?

Yes, you can improve delivery discipline and reduce meta-work by detecting when team members describe tasks, converting those planning descriptions into immediate execution, and logging verifiable results.

What's the best way to convert planning descriptions into immediate execution?

The best way to convert planning into immediate execution is to provide concrete counter-actions that force team members to perform the task first and document verifiable outcomes only after completion.

Why does my team spend more time documenting work than actually doing it?

Your team spends more time documenting work than doing it due to a lack of execution discipline, which can be fixed by applying an action bias that forces immediate action and logs outcomes before reporting completion.