long-running-agent-workflow

Solid

Structured protocol for AI agents working across many context windows: a .lra/ directory with an atomic feature list (id/priority/acceptance criteria/status) and a session progress log, plus a session protocol (read context → pick ONE feature → implement → test → checkpoint) and recovery from broken states. Based on Anthropic research on long-running agents. Triggers: 'lra', 'checkpoint', 'feature list', 'long running', 'продолжи работу', 'долгая сессия', 'план фич', 'статус проекта'.

AI & Automation 5 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
26
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Long-Running Agent (LRA) Workflow Load this skill when you are about to work on a **large project that will span multiple sessions / context windows** and you need continuity, atomic handoffs, and recovery from broken states. The skill gives you a tiny CLI (`scripts/lra_cli.py`) that maintains a `.lra/` directory: a machine-readable `feature-list.json` (atomic features with acceptance criteria and status) and a human/agent-readable `progress.txt` (session log). The protocol turns "one big vague task" into a sequence of small, fully-tested, check-pointed features. --- ## Overview — the problem AI agents working across many context windows hit three failure modes: - **Context amnesia** — each new session has no memory of prior work. - **One-shot tendency** — trying to do too much at once, leaving half-done features. - **Incomplete features** — work spans sessions with no clear acceptance gate, so "done" is never verified. LRA fixes this with: structured init, one atomic feature per session, an explicit test gate before `done`, and a checkpoint after every feature so the next session can recover. --- ## When to use - Long, multi-session projects (hours/days, many context windows). - Any task where you might lose context between runs. - Triggers: `lra`, `checkpoint`, `feature list`, `long running`, `продолжи работу над проектом`, `долгая сессия`, `план фич`, `статус проекта`. If the task is small and finishes in one session, you do **not** need this skill — jus...

Details

Author
bestdeejay-design
Repository
bestdeejay-design/agent-skills
Created
1 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

long-task-continuation

Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.

1,179 Updated yesterday
GanyuanRan
AI & Automation Listed

workflow

Bootstrap and manage multi-agent workflow configurations across projects. Use this skill when the user asks to set up agent roles, generate an AGENTS.md, configure background dispatch policies, or apply a pre-defined multi-agent architecture (e.g. 5-agent strategist pattern) to a new or existing project. Invoke for requests like "set up agents in this project", "create AGENTS.md", "bootstrap workflow", "show available workflows", "validate AGENTS consistency", or "refresh agent config after upstream changes". Русские триггеры (контур работает по-русски) — «настрой агентов в проекте», «сгенерируй AGENTS.md», «разверни мультиагентную архитектуру в этом репозитории», «покажи доступные workflow-шаблоны», «сверь AGENTS.md с шаблоном», «обнови конфиг агентов». РАЗГРАНИЧЕНИЕ — этот скилл ГЕНЕРИРУЕТ ШАБЛОНЫ ролей и ничего не спавнит; фактический параллельный запуск субагентов делает встроенный инструмент `Workflow(...)`, разные вещи с похожим именем. Разовый многоисточниковый разбор вопроса субагентами → скилл `deep-

0 Updated today
VibeEngineering-LLC
AI & Automation Listed

long-run

Set up a long-running multi-agent orchestrator that builds a project end-to-end across many /loop cycles. Use when the user wants to "kick off an overnight build", "start a weekend run", "set up the orchestrator harness", "run a long autonomous build", or any task framed as "let Claude build this while I sleep". Hard-requires a detailed milestone roadmap before kickoff — if the user lacks one, this skill stops and routes them to write one (it does NOT auto-generate the roadmap). Uses Git as the source of truth; expects the app, docs, marketing site, tests, and screenshots to live in the same repo so the prototype's assets evolve together. Do NOT apply to short one-shot tasks, single PRs, or anything that can finish in one Claude turn.

1 Updated 1 months ago
reidworks-io