git404hub

what is future-regret fr?

acost1a/future-regret — explained in plain English

Analysis updated 2026-05-18

1ShellAudience · developerComplexity · 1/5LicenseSetup · easy

tl;dr

A Claude Code skill that role-plays future-you interrogating an architecture decision, then files a dated regret report before you commit.

vibe map

mindmap
  root((future-regret))
    What it does
      Interrogates decisions
      Writes regret reports
      Verdicts on risk
    Tech stack
      Claude Code
      Markdown skill
    Use cases
      Stress test architecture choices
      Track past decisions
      Avoid costly mistakes
    Audience
      Developers
      Solo builders
    Verdicts
      REGRET
      HEDGE
      SHIP

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 make with this?

VIBE 1

Stress-test a proposed database or architecture decision before implementing it.

VIBE 2

Generate a dated regret report documenting a decision's risks, warning signs, and cheapest fix.

VIBE 3

Keep a searchable record of past architecture decisions to check later which predicted problems actually happened.

what's the stack?

Claude CodeMarkdown

how it stacks up fr

acost1a/future-regret100/dotfilesabdellaouiamir/palworld-server
Stars111
LanguageShellShellShell
Last pushed2016-11-18
MaintenanceDormant
Setup difficultyeasyeasymoderate
Complexity1/51/53/5
Audiencedeveloperdeveloperops devops

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

how do i run it?

Difficulty · easy time til it works · 5min

Installs as a Claude Code plugin or a manually copied markdown skill file, no infra required.

MIT license: use freely for any purpose, including commercial use, as long as you keep the copyright notice.

in plain english

future-regret is a skill for Claude Code, the AI coding assistant, that challenges architecture decisions before you commit to them. Instead of letting the AI simply agree with a plan or list a few pros and cons, it plays the role of a future version of you, six months after the decision was made, and interrogates it one sharp question at a time until any weak point is exposed. After the questioning, it writes a dated report into your repository describing a realistic failure that could result from the decision, the warning signs to watch for in your codebase, and the cheapest way to fix or avoid it. The project states that every failure scenario it describes is based on a real, verified technical failure mode rather than an invented scary story, and that a dispatch gets deleted rather than kept if it cannot be backed up this way. Each review ends with one of three verdicts. REGRET means the decision is hard to undo and likely to cause real pain later. HEDGE means the decision is acceptable only if a specific cheap safeguard is added now. SHIP means the decision is safe or easily reversible and can proceed as planned. The written report is saved as a markdown file in a docs/regrets folder, timestamped and named after the decision, so it becomes a searchable record you can revisit later to check whether the predicted problems actually happened. The entire tool is a single markdown skill file rather than a standalone application. It installs directly into Claude Code through the plugin marketplace, or can be copied manually into any tool that supports markdown-based skills. Once installed, it can be triggered manually or activates on its own when a user proposes an architecture decision during a coding session.

prompts (copy fr)

prompt 1
Install and run future-regret on my plan to store all analytics events in one JSONB column.
prompt 2
Explain how future-regret decides between the REGRET, HEDGE, and SHIP verdicts.
prompt 3
Show me how a dispatch file gets written to docs/regrets and what it contains.
prompt 4
Have future-regret interrogate this architecture decision before I commit to it.

Frequently asked questions

what is future-regret fr?

A Claude Code skill that role-plays future-you interrogating an architecture decision, then files a dated regret report before you commit.

What language is future-regret written in?

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

What license does future-regret use?

MIT license: use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is future-regret to set up?

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

Who is future-regret for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.