longrunning-agent_skill

This skill helps AI agents manage long-running projects by tracking progress, prioritizing tasks, and sustaining momentum across sessions.
  • Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill longrunning-agent

  • _meta.json648 B
  • manifest.json667 B
  • SKILL.md2.9 KB

Overview

This skill enables AI agents to run long-running projects across multiple sessions with reliable continuity. It provides structured task tracking, priority and dependency management, and a simple session-based progress log to drive incremental, testable work.

How this skill works

The agent inspects a project directory for a workflow set: a human-readable project guide, a task list (JSON) with priorities and dependencies, and a progress log. Each session the agent reads progress, picks the next unmet task whose dependencies are satisfied, runs any initialization, makes a small atomic change, tests, documents the result, and marks the task complete. Commits are kept per-task to preserve atomic history.

When to use it

  • When projects span hours, days, or weeks and need persistent state between sessions.
  • For complex features that must be decomposed into dependent, testable steps.
  • When multiple agents or humans may resume work and need clear handoff state.
  • To enforce single-task-per-session discipline for reliable progress tracking.
  • When reproducible, atomic commits are required for auditability.

Best practices

  • Work on exactly one task per session to keep changes atomic and reviewable.
  • Maintain concise progress entries with timestamps and outcomes.
  • Define explicit dependencies in the task JSON to enforce order.
  • Run linting, builds, and tests before marking a task as passed.
  • Commit after each completed task with a clear message referencing the task id.

Example use cases

  • Incrementally implementing a new product feature split into dependent subtasks.
  • Refactoring a large codebase where each session applies and tests a single refactor step.
  • Documenting and delivering research or writing projects across multiple sittings.
  • Coordinating multi-agent workflows where agents pick next available tasks automatically.
  • Maintaining a reproducible backup or archive workflow with logged progress and commits.

FAQ

A project guide file, a task JSON with id/priority/dependencies, and a progress log. An optional init script can be used for environment setup.

How are dependencies enforced?

The agent selects the next task only if all listed dependency ids are marked as completed (passes: true) in the task JSON.

How should progress entries be written?

Keep entries short, timestamped, and focused on what changed and what remains. Example: '[YYYY-MM-DD HH:MM:SS] Completed task: task-3 — added tests and updated docs.'

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational