Skip to content

AgriciDaniel/agentic-habits / skills/habits

Agentic habits. Give an agent standing behavior that survives the end of a chat, in three tiers: stated rules placed where their trigger fires, gates that make the ones that must not fail deterministic, and an evidence-bound judge that scores adherence from a fresh context. Use for /habits, and whenever someone says from now on, always do this, stop doing that, remember to, make this stick, agent habits, bad habits, how do I know you actually did it, or asks why the agent keeps repeating a mistake.

assets/templates/decision.md

View on GitHub
---
type: decision
title: "<what was decided>"
status: current
created: <YYYY-MM-DD>
updated: <YYYY-MM-DD>
tags: ["#type/decision"]
related: ["<HABIT-ID>", "<case ids this bears on>"]
---

# <what was decided>

## Decision

One sentence. What changed, at what scope, from when.

## Why, without reference to the failure it produced

If this is a change to a habit's `check`, the reason must stand on its own. "The
check was wrong because it counted an attempted command as a completed one" is a
reason. "The check kept failing" is not, and a decision record that gives the
second one is a record of grader tampering with better formatting.

## What this invalidates

- Lapse history measured against the old version: reset to a dash, and say so.
- Cases that cited the old wording: they stay, unedited. A case is evidence and
  evidence is not revised to match a later decision.
- Any gate whose script encoded the old check.

## Re-baseline

State the new starting point: which habit, which check, which date, and what the
next judged run will be measured against.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall