pa-ownership

Track Heleni's committed tasks with retries and completion reports in pa-tasks.json.

5|1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/netanel-abergel/pa-skills --skill pa-ownership
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pa-ownership
Source: https://github.com/netanel-abergel/pa-skills/tree/main/skills/pa-ownership
Command: npx skills add https://github.com/netanel-abergel/pa-skills --skill pa-ownership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Heleni often takes ownership of tasks that require persistent tracking, retry until resolution, and clear reporting back to the initiator. This skill provides a structured workflow to manage such tasks end-to-end.

Core Features & Use Cases

  • End-to-end task lifecycle: creation, in-progress work, retry on blockers, and completion reporting.
  • Close-the-loop notifications: always inform the task initiator whether the task is completed, blocked, or failed.
  • Persistent state & heartbeat: stores tasks in pa-tasks.json and integrates with heartbeat to surface stale items for remediation.

Quick Start

Tell Heleni to take ownership of a task by providing a title and description, then confirm the details.

Frequently Asked Questions about pa-ownership

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

FAQPage Schema
How do I automate task ownership tracking with retries and notifications?

Automated task ownership tracking manages the full lifecycle from initiation to completion, using backoff-based retries for blockers and sending close-the-loop notifications to the initiator via direct message or group thread.

What is the best way to track stale tasks using a heartbeat integration?

Tracking stale tasks with a heartbeat integration involves storing all task states in a persistent pa-tasks.json file, allowing the system to surface items that lack recent progress for timely remediation.

How do I get notified when an automated task is blocked or fails?

To get notified when an automated task is blocked or fails, the ownership system monitors task states and actively alerts on BLOCKED or FAILED conditions, ensuring the initiator is always informed.

Can I manage persistent task state without external dependencies?

Yes, you can manage persistent task state without external dependencies by storing all ownership records, retry counts, and progress data locally in a pa-tasks.json file.

How does close-the-loop reporting work for task completion?

Close-the-loop reporting for task completion works by automatically sending a final status update back to the original initiator, confirming whether the tracked task was successfully completed, blocked, or failed.

When do I need automated retry logic for task tracking?

You need automated retry logic for task tracking when committed items encounter transient blockers, requiring a structured backoff mechanism to attempt resolution before alerting a FAILED state.