journal

Record progress, decisions, and risks in .topia state files.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill journal-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journal
Source: https://github.com/linenoize/topia/tree/main/skills/journal
Command: npx skills add https://github.com/linenoize/topia --skill journal-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill preserves progress, decisions, risks, and architecture notes across AI sessions so work does not vanish when context is lost or a task spans multiple sittings.

Core Features & Use Cases

  • Durable session state: Tracks rescue progress, module health, and pending work in .topia/ files.
  • Decision logging: Creates architecture decision records only when a choice is significant enough to deserve long-term context.
  • Risk tracking: Records technical, schedule, dependency, and security risks with mitigation and trigger conditions.
  • Dependency awareness: Keeps the dependency graph aligned when module relationships change.
  • Use case: A developer can resume a half-finished rescue, audit, deploy, or feature workflow and immediately recover the last known state, decisions, and open risks.

Quick Start

Ask the journal skill to record the current session’s progress, decisions, and risks into the appropriate .topia/ files.

Frequently Asked Questions about journal

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

FAQPage Schema
How do I persist architecture decision records across multiple AI sessions?

To persist architecture decision records across AI sessions, use a journaling skill that logs significant choices into durable state files. It records ADRs, risks, and progress so work is not lost when context is reset.

What is the best way to track technical risks and progress in long-running software workflows?

Tracking technical risks and progress in long-running workflows requires maintaining risk logs with trigger conditions and mitigation strategies. A journal skill records these alongside dependency graphs in local state files for later recovery.

How do I recover session state after losing context during a deployment or incident rescue?

Recovering session state after context loss involves reading persisted progress and decisions from local files. The journal skill maintains durable state in a local directory, allowing you to resume rescue, deploy, or incident workflows immediately.

Does the journal skill require external dependencies to sync decision logs?

The journal skill does not require external dependencies to function, but supports optional agora-code MCP sync. It natively manages state files, ADRs, and dependency graphs locally without needing additional packages.

When should I use architecture decision records for software engineering tasks?

You should use architecture decision records when a technical choice is significant enough to deserve long-term context. The journal skill captures these durable decisions only when they materially impact future sessions.

Can I track dependency graph changes alongside module health during a code audit?

Yes, you can track dependency graph changes and module health during a code audit. The journal skill keeps the dependency graph aligned when module relationships change and records health status in local state files.