Update run status fields in .runs/index.json for a given run_id.
npx skills add https://github.com/EffortlessMetrics/demo-swarm --skill runs-index
Please help me install this Agent Skill. Skill: runs-index Source: https://github.com/EffortlessMetrics/demo-swarm/tree/main/.claude/skills/runs-index Command: npx skills add https://github.com/EffortlessMetrics/demo-swarm --skill runs-index
This Skill automates the structured tracking of development run statuses, eliminating the manual effort and inconsistencies associated with keeping project progress visible and auditable. It ensures your .runs/index.json is always current.
status, last_flow, and updated_at fields within .runs/index.json for a given run_id.index.json to reflect the latest status (e.g., "VERIFIED") and the last completed flow for a specific run, providing real-time project visibility and audit trails.Update the index.json for run 'feat-auth' to status 'VERIFIED' after the 'signal' flow, using the current timestamp generated by the 'time now' command.
High-intent search queries and answers about installing and using this skill.
Run status updates are performed by upserting to `.runs/index.json`, modifying only `status`, `last_flow`, and `updated_at` fields for a given `run_id`. This automation eliminates manual tracking and keeps project progress visible and auditable throughout your SDLC workflows.
Deterministic updates ensure consistent field ordering and minimal file changes, producing stable diffs in version control. This makes it clear what changed in each run without noisy or unpredictable modifications to your index.
Yes. The tool modifies only designated fields—`status`, `last_flow`, and `updated_at`—while preserving other run metadata owned by other agents, ensuring controlled writes and preventing accidental data loss.
Invoke it at the conclusion of SDLC flows, such as after cleanup or signal steps, to reflect the latest run status (e.g., 'VERIFIED') and last completed flow for real-time visibility and audit trails.
The `.runs/index.json` file must exist before use. The tool requires repo-root relative paths and ensures idempotent updates, emitting 'ok' with exit code 0 on success or an error message with non-zero code on failure.
No. It updates existing fields only and does not create new files or fields, maintaining a stable, predictable index structure aligned with your SDLC automation.
cuiossTrack plan status and phase lifecycle in a JSON store.
kevinslinSend macOS desktop notifications for task completion, input, and errors via terminal-notifier.
pangonGenerate a project-wide SDLC status report with artifact counts and phase gate readiness.
TeamWiseFlowManages persistent customer records and follow-up tasks in a SQLite database.