rune-journal

Records architecture decisions, risks, and progress state across sessions in .rune files.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-journal-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-journal
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-journal
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-journal-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long-running engineering work loses context between sessions: decisions get forgotten, progress tracking resets, and future engineers cannot tell why a tradeoff was made. This Skill persists decisions, risks, and module health as durable, human-readable files that survive session boundaries and context compaction. ## Core Features & Use Cases - Gated ADR creation: Scores each decision on reversibility, surprisingness, and tradeoff strength (3-15 scale) and only writes an ADR when the score reaches 11 with a credible rejected alternative, keeping the ADR directory free of noise. - Risk register: Logs identified risks with severity, likelihood, mitigation actions, trigger conditions, and contingency plans, with a classification matrix that forces deadlines on critical items. - Progress and dependency tracking: Maintains RESCUE-STATE.md, module-status.json, and a Mermaid dependency graph so any new session can recover full project state. - Use Case: After a multi-session refactoring effort, a new session reads the .rune directory and immediately knows the current phase, module health scores, open risks, and the rationale behind prior architectural choices. ## Quick Start Record the architectural decisions and progress from this session into the .rune directory, opening ADRs only for decisions that pass the scoring gate.

Frequently Asked Questions about rune-journal

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

FAQPage Schema
How do I decide when to write an architecture decision record?

Score the decision on three axes from 1 to 5: reversibility, surprisingness, and tradeoff strength. Open an ADR only when the total is at least 11 and every axis is at least 3, and you can name a credible rejected alternative that was actually considered.

How do I preserve project context across AI sessions?

Store progress in human-readable state files like RESCUE-STATE.md and module-status.json, plus ADR and risk files. A new session reads these files first, recovering phase, module health scores, open risks, and past decisions with zero context loss.

What is the difference between an ADR and a convention?

An ADR captures a real tradeoff at a fork point with credible rejected alternatives, while a convention is an obvious choice everyone makes the same way. Conventions belong in CLAUDE.md or code comments, not in the ADR directory.

What should a risk register entry contain?

Each risk entry needs severity, likelihood, status, a specific description of what could go wrong, quantified impact, mitigation actions with owners and deadlines, trigger conditions for detection, and a contingency plan if the risk materializes.

Can an ADR file be overwritten or updated later?

No, existing ADR files must never be overwritten. When recording a new decision, the sequence number increments to the next available NNN, preserving the full history of prior decisions for future sessions.