From rpw-working
HUMAN task management — canonical operating model for the human's work backlog. Use when setting up task tracking, selecting or creating the GitHub repository for tasks, updating task status, handing off work between sessions, or triaging backlog.
npx claudepluginhub randypitcherii/rpw-agent-marketplace --plugin rpw-workingThis skill uses the workspace's default tool permissions.
**HUMAN task management.** This skill defines the canonical operating model for the human's task system (GitHub Issues + Project). The human owns and manages their tasks; agents operate within this model to create, update, and sync task state.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Builds scalable data pipelines, modern data warehouses, and real-time streaming architectures using Spark, dbt, Airflow, Kafka, and cloud platforms like Snowflake, BigQuery.
Builds production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. For data pipelines, workflow orchestration, and batch job scheduling.
HUMAN task management. This skill defines the canonical operating model for the human's task system (GitHub Issues + Project). The human owns and manages their tasks; agents operate within this model to create, update, and sync task state.
Persist task-system configuration in a local, user-managed file:
~/.claude/rpw-working.local.md (global, in user's home directory)Minimum frontmatter fields:
---
enabled: true
github_owner: "your-github-user-or-org"
github_repo: "your-private-tasks-repo"
github_repo_url: "https://github.com/your-github-user-or-org/your-private-tasks-repo"
github_project_number: 3
project_title: "All Tasks"
ignore_label: "ignore_in_tasks_views"
execution_state_field: "Execution State"
priority_field: "Priority"
impact_field: "Impact"
---
If the state file is missing, incomplete, or points to an inaccessible/missing repository, agents should run setup flow before doing task operations.
All Tasks.ignore: apply ignore_in_tasks_views label and filter task views to exclude itconvert: normalize existing issues into this model (state/priority/impact where possible); for epic-based repos, use the epic-to-milestone bootstrap (see below)delete: only after explicit confirmation~/.claude/rpw-working.local.md.When convert is selected and the repo has legacy epic issues, bootstrap milestone-based tracking:
- Type: epic in body, or title prefix Epic: as fallback.Blocked by #<epic> and Part of #<epic>.Epic: prefix stripped.Blocked by #<epic> lines from child issue bodies when the epic was deleted.Safety rule: Destructive deletion (epics, issue content) happens only in this convert flow and only after explicit user confirmation. Never delete without confirmation.
See references/epic-to-milestone-migration.md for the migration checklist.
Before task operations, validate state by checking:
If any check fails, stop task operations, explain what failed, and re-run setup flow to repair state.
Use gh as the default interface:
# List private repos for the current user
gh repo list <owner> --visibility private --limit 100
# Create a new private repo
gh repo create <owner>/<repo> --private --confirm
Use gh project / gh api graphql as needed to ensure project fields and All Tasks view exist.
Use these project field values for board movement:
| Value | Meaning |
|---|---|
Backlog | Not yet scheduled |
To Do | Scheduled, ready to start |
In Progress | Actively being worked on |
Now | Current focus, used sparingly |
Done | Completed |
blocked label on the issue.Example handoff comment:
**Handoff**
- State: In Progress, ~60% done
- Next: Implement validation in `src/validate.py`
- Blocker: None
0-100 scale on project fields.~/.claude/rpw-working.local.md before task operations.blocked label for blocked work.