johnwangwyx

Stele — Documentation skill for Claude Code

Documentation community

Rate limited mid-task.

How to install Stele

This entry records only its repository, not the path inside it, so there is no exact command to give. Open johnwangwyx/stele and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Stele does

Rate limited mid-task? Crashed mid-edit? Locked into one harness by the context it holds? A skill that keeps task state in plain markdown, written before the work rather than at exit — so any agent resumes cold. Claude Code, Codex, Cursor.

Alternatives in Documentation

  • Docx — Create, edit, and analyze Word documents with tracked changes, comments, and formatting 94.1k ★
  • Repo Recap — Generate a structured recap of the repository state: open PRs, open issues, recent releases, and executive sum 11.9k ★
  • Skills Quick Reference Guide — A guide for choosing the right skill for your task 6.8k ★

README

stele

**Durable task state for AI coding agents, as a skill.**

One task across two sessions, both running stele. Three writes land on disk before the work they describe: opening step 2, closing it, opening step 3. A rate limit interrupts with step 3 still open. A second session in a different harness resumes, reads the open step to see what was half-applied, and finishes and closes it.

Existing solutions write the record last: a handoff skill at the end of a session, a summary before you close the laptop. That works right up until the session ends without you — a usage limit, a crash — and then there is nothing at all. Writing first makes you resumable at every point, not just the ones you planned for.

Install

Since you are already here, and you have an agent. Install in one line. 😉

Install https://github.com/johnwangwyx/stele as a skill under your framework.

To use

1. Start managing a project

`/stele` manage this project with stele

`/` is Claude Code — Codex uses `$stele`, and other harnesses have their own way to start conversation while mentioning a skill.

New project, same sentence. On an existing repo the skill reads what is already there.

2. Now it is interruptible

Hit a usage limit, crash, close the laptop, switch provider, come back in three weeks. The record is already on disk, because every write happened *before* the work it describes rather than after it. Nothing needs saving on the way out.

3. Resume, in any harness

`/stele` resume where it is left off

Note: You will mostly not even need the skill trigger (`/stele` or `$stele`). That first run left a p