explaingit

alicicek/tale-mode

Analysis updated 2026-05-18

19ShellAudience · developerComplexity · 2/5Setup · easy

TLDR

A Claude Code plug-in that scales how much process a coding task gets, from a quick fix to a full review loop for high-stakes changes.

Mindmap

mindmap
  root((repo))
    What it does
      Throttles process by task risk
      Full 8-step review loop
      Independent adversarial review
    Tech stack
      Shell scripts
      Claude Code
    Use cases
      Quick fixes without ceremony
      Careful handling of risky changes
      Multi-phase feature planning
    Audience
      Claude Code users
      Developers
    Commands
      slash plan-phase
      slash kickoff-phase

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Let a coding agent decide automatically how much verification a task needs before starting.

USE CASE 2

Trigger an independent adversarial review before shipping payments, auth, or security changes.

USE CASE 3

Plan a large feature into independently shippable phases with /plan-phase.

USE CASE 4

Resume a phase in a fresh session with /kickoff-phase and re-verify the plan against current code.

What is it built with?

ShellClaude Code

How does it compare?

alicicek/tale-modevigneshwari-08/server_log-analyzer-intrusion-detectorabuzar-ansarii/androidlinux-gpu
Stars191920
LanguageShellShellShell
Setup difficultyeasyeasymoderate
Complexity2/52/52/5
Audiencedeveloperops devopsdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

The independent-reviewer sub-agent feature needs a host that supports sub-agents, like Claude Code.

In plain English

Tale Mode is a plug-in behavior for Claude Code, the AI coding assistant, that tries to make the model work more carefully on complex tasks. It was created after Anthropic discontinued a Claude variant called Fable, and it aims to bring the disciplined working style that Fable was known for to the current Opus model. The core idea is a throttle that decides how much process a task deserves before starting it. A typo fix gets no ceremony: the model just fixes it. A multi-file refactor triggers a lighter process with verification steps. Anything touching payments, authentication, or security, or anything that would be hard to reverse, triggers the full loop, which includes a separate independent review pass before any code ships. The full loop runs eight steps: mapping the work and defining what "done" looks like before acting, attaching a cited source or an explicit judgment label to every decision, splitting independent work to sub-agents when appropriate, verifying both internal consistency and against the actual files on disk rather than relying on the model's memory of them, running a self-critique and, for high-stakes tasks, a fresh adversarial reviewer that reads the code independently without the original context, surfacing genuine forks in the work to ask the user rather than guessing, saving progress to a durable file, and naming anything that was not tested or verified. The skill also ships two slash commands. "/plan-phase" produces a plan for a larger feature and breaks it into independently shippable phases. "/kickoff-phase" picks up one phase in a fresh session, re-verifies the plan against the current state of the code, asks questions at real decision points, and waits for approval before writing anything. The README recommends clearing context between phases because a long session re-reads its entire history on every turn, which slows it down. Installation is a git clone followed by running an install script. The independent reviewer feature requires a host that supports sub-agents, which Claude Code provides. On the claude.ai web interface, it falls back to a fresh-frame self-review instead.

Copy-paste prompts

Prompt 1
Use tale-mode to decide how much process this task needs before you start.
Prompt 2
Run /plan-phase to break this feature into independently shippable phases.
Prompt 3
Run /kickoff-phase to pick up phase 2 and re-verify the plan against the current code.
Prompt 4
Trigger the full review loop on this change since it touches authentication.

Frequently asked questions

What is tale-mode?

A Claude Code plug-in that scales how much process a coding task gets, from a quick fix to a full review loop for high-stakes changes.

What language is tale-mode written in?

Mainly Shell. The stack also includes Shell, Claude Code.

How hard is tale-mode to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is tale-mode for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.