rituales

Documents and executes five CLAUDEMAX lifecycle rituals for session, day, and sprint closure.

Updated May 19, 2026
One-click install
npx skills add https://github.com/Curcolor/CLAUDEMAX --skill rituales-curcolor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rituales
Source: https://github.com/Curcolor/CLAUDEMAX/tree/main/skills/rituales
Command: npx skills add https://github.com/Curcolor/CLAUDEMAX --skill rituales-curcolor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work sessions in Claude Code lose context when they end, and teams lack a consistent way to record what was done, what comes next, and when to reindex the knowledge base. This Skill documents the five CLAUDEMAX lifecycle rituals and the exact commands to run each one. ## Core Features & Use Cases - Session continuity notes: The fin-sesion ritual writes a timestamped note to the vault's 00-Inbox folder with what was done and the next step, so the next session resumes without losing context. - Daily journal entries: The fin-dia ritual appends time-stamped entries to a daily Journal note without overwriting previous entries. - Sprint closure with reindexing: The fin-ciclo ritual writes a cycle-closure note and reindexes the RAG base, but only after explicit confirmation via the --si flag. - Project initialization: The init-proyecto ritual scaffolds .claude config files and a vault index note for a new project without overwriting existing files. - Use Case: At the end of a work session, say "fin de sesión" and the Skill tells you to run node R.A.G/ritual.mjs fin-sesion --resumen "..." --siguiente "..." to persist the session state. ## Quick Start Ask the assistant to run the end-of-session ritual with a summary of what was accomplished and the next step to resume later.

Frequently Asked Questions about rituales

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

FAQPage Schema
How do I save session context before closing Claude Code?

Run node R.A.G/ritual.mjs fin-sesion with --resumen describing what was done and optionally --siguiente for the next step. It writes a timestamped note to V.A.U.L.T/00-Inbox so the next session can resume the thread.

What is the difference between fin-sesion and fin-dia rituals?

fin-sesion closes a single work session and can run multiple times per day, writing to 00-Inbox. fin-dia closes the whole workday, appending a time-stamped entry to the daily Journal note.

Does fin-ciclo reindex the RAG database automatically?

No. fin-ciclo only prints the plan by default and touches nothing. It reindexes the RAG base and writes the closure note only when you pass the --si flag, making it the only ritual requiring explicit confirmation.

What happens if I run fin-sesion without a summary?

The ritual does not fail. It writes the note with an empty template containing a placeholder in the "Qué se hizo" section and clearly reports this in the console so you can fill it in manually.

Will init-proyecto overwrite my existing .claude config files?

No. init-proyecto never overwrites existing files. If .claude/CLAUDEMAX.md, .claude/CLAUDE.md, or the vault index note already exist, it respects them, reports this in the console, and continues with the remaining steps.