living

Appends terse, agent-readable session summaries to a project's living.md file.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/jpmoya/claude-agents --skill living-jpmoya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: living
Source: https://github.com/jpmoya/claude-agents/tree/main/skills/living
Command: npx skills add https://github.com/jpmoya/claude-agents --skill living-jpmoya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Session context disappears when a work session ends, forcing the next agent or developer to rediscover decisions, findings, and open items. This Skill records what shipped, what was decided, and what remains unresolved in a structured living.md log optimized for future agent readers. ## Core Features & Use Cases - Structured Session Entries: Appends dated entries using SHIP, DEC, FIND, OPEN, FILES, and LESSON tags with strict formatting rules. - Token-Efficient Format: Enforces terse, fact-dense writing that preserves identifiers (IDs, SKUs, PR numbers, file paths) while dropping filler prose. - Auto-Discovery: Locates living.md at the repo root via git, or creates it with a standard header if missing. - Use Case: After a long debugging and implementation session, ask the agent to update living.md so the next session starts with full context on what changed and why. ## Quick Start Say "update living" at the end of a work session to append a structured summary of what was done to the project's living.md.

Frequently Asked Questions about living

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

FAQPage Schema
How do I update living.md after a work session?

Say "update living" or "update living.md" and the skill appends a dated entry at the top of the file. It gathers context from recent git commits and the conversation, then writes SHIP, DEC, FIND, OPEN, FILES, and LESSON lines.

What format does a living.md session entry use?

Each entry starts with a date and kebab-case slug, followed by tagged one-line facts: SHIP for delivered work, DEC for decisions with reasons, FIND for discoveries, OPEN for unresolved items, FILES for changed paths, and optional LESSON for reusable insights.

Does the living skill work in any project repository?

Yes, it works for any project by locating living.md at the git repo root via git rev-parse. If the file does not exist, it creates one with a standard header before appending the entry.

Why does living.md avoid bold text and prose paragraphs?

The file is written for future agents, not humans, so it optimizes for facts per token. Bold, italics, and filler phrases add markup cost without information, while identifiers like IDs and figures are always preserved verbatim.

Should living.md entries be committed automatically?

No, the skill does not commit living.md after writing. The user commits it manually or folds it into the next pull request, keeping the log under explicit human control.