project-participation

Coordinate multi-worker project tasks using plan.md and git attribution.

5.3k|652|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill project-participation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-participation
Source: https://github.com/agentscope-ai/HiClaw/tree/main/manager/agent/hermes-worker-agent/skills/project-participation
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill project-participation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps workers quickly understand a shared project plan, align task status and ownership across multiple Workers, and ensure their code contributions are correctly attributed.

Core Features & Use Cases

  • Project plan auto-read from shared storage: Use the synchronized plan.md file stored under the MinIO-backed shared path to know tasks, dependencies, and statuses.
  • Task coordination and completion reporting: Follow the workflow from assignment to completion, advancing the project by notifying the coordinator via @mention.
  • Correct git author attribution for traceability: Configure git user.name and user.email to match the worker name so commits are identifiable.

Quick Start

Use the project plan stored at ~/shared/projects/{project-id}/plan.md to identify your assigned task, then complete it and report completion to your coordinator via @mention.

Frequently Asked Questions about project-participation

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

FAQPage Schema
How do I coordinate tasks in a multi-worker project using a shared filesystem?

To attribute commits correctly in multi-worker projects, set your git user.name and git user.email to match your assigned worker name before committing. This ensures all code contributions are identifiable and traceable across the shared project workflow.

What is the workflow for reporting task completion to a project coordinator?

Task status tracking in multi-agent coordination relies on a synchronized plan.md file stored under a MinIO-backed shared path at ~/shared/projects/{project-id}/plan.md. Workers read this file to identify assigned tasks, dependencies, and current project statuses.

Can I use this multi-agent coordination workflow without a shared storage backend?

Multi-agent coordination requires a locally auto-synced shared filesystem backed by MinIO to access the plan.md file. Without this shared storage path, workers cannot read project plans, track task statuses, or participate in the shared Manager-Workers workflow.

Why does git author attribution matter in shared project workflows?

Git author attribution in shared project workflows ensures code contributions are correctly traced to specific workers. By configuring git user.name and user.email to match the worker name, teams maintain clear ownership and accountability across multi-worker task execution.