Command Claude Code
Create a new technical debt entry in TECHDEBT.md at the beginning of this file using the following standardized structure.
5 5d ago A 0 tokens
5Stars on the repository
12Mods indexed here, across every type
5d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied
deduplicated
02Command Claude Code
Review all existing problem descriptions and identify entries that describe essentially the same issue, even if expressed differently. When two or more problems appear to be closely related, propose merging them into a single, coherent problem entry. For each suggestion, preserve the most complete title, symptoms, and…
5 5d ago A 0 tokens
Command Claude Code
Continue by creating at least 20 new problem descriptions for legacy software systems using the existing pattern template. First, review scripts/backlog/new.md when it exists and generate entries based on its contents. Then browse the current problem descriptions and prioritize detailing issues mentioned in the…
5 5d ago A 0 tokens
Command Claude Code
Inspect the Symptoms and Causes sections of problems/.md and connect mentions to existing problem files. This command maintains the representation of the causal graph; it does not establish that a causal relationship is true.
5 5d ago A 0 tokens
Command Claude Code
Go through each problem and focus on the Category entry. Read the title and its short description, then reorder the positions within the category list based on which category the title fits best. Remove any categories that don’t make sense, and add missing ones if needed; retain existing ones if they seem appropriate.…
5 5d ago A 0 tokens
Command Claude Code
Review causal relationships in problems/ for validity. Treat every relationship as a hypothesis, including relationships recorded reciprocally in both problem files. Reciprocity establishes structural consistency only; it is not independent evidence that the relationship is true.
5 5d ago A 0 tokens