← Back to list

task-metadata
by frizynn
A high-performance implementation of the Ralph autonomous loop. Orchestrates multi-agent execution across Claude Code and Cursor, utilizing Git worktree isolation to scale PRD-driven development.
⭐ 13🍴 0📅 Jan 20, 2026
SKILL.md
name: task-metadata description: "Generate and validate task metadata for Ralph parallel execution. Use when creating tasks.yaml v1 files, validating task dependencies, or checking mutex usage. Triggers on: create task metadata, validate tasks yaml, check task dependencies."
Task Metadata Generator
Create and validate task metadata for parallel-safe execution in Ralph.
The Job
- Generate or validate
tasks.yamlv1 metadata - Ensure unique task IDs
- Validate dependencies exist
- Check mutex against catalog
- Output clear errors for invalid metadata
Do NOT: schedule tasks, merge branches, or review design.
tasks.yaml v1 Format
version: 1
tasks:
- id: US-001
title: "Short descriptive title"
completed: false
dependsOn: [] # Array of task IDs that must complete first
mutex: [] # Array of mutex names from catalog
touches: [] # Optional: paths/globs this task modifies
contracts: # Optional: interface contracts
produces: []
consumes: []
mergeNotes: "" # Optional: hints for conflict resolution
verify: [] # Optional: verification commands
Required Fields
| Field | Type | Description |
|---|---|---|
id | string | Unique identifier (e.g., US-001, TASK-1) |
title | string | Human-readable task name |
completed | boolean | Task completion status |
dependsOn | array | Task IDs that must complete before this one |
mutex | array | Mutex names from the catalog |
Mutex Catalog
Valid mutex names (check mutex-catalog.json):
db-migrations- Database schema changeslockfile- Package lock files (package-lock.json, yarn.lock, etc.)router- Route configuration filesglobal-config- Global configuration filescontract:*- Interface contracts (e.g.,contract:auth-api)
Validation Checklist
When validating tasks.yaml:
-
version: 1is present - Every task has
id,title,completed,dependsOn,mutex - All
idvalues are unique - All
dependsOnreferences exist as task IDs - No circular dependencies
- All
mutexvalues exist in catalog
Output Format
Valid Metadata
✓ tasks.yaml v1 valid
- 5 tasks
- 3 unique mutex
- 2 dependency chains
Invalid Metadata
✗ tasks.yaml validation failed:
- Line 12: Duplicate id "US-001"
- Line 25: dependsOn "US-999" not found
- Line 30: Unknown mutex "invalid-mutex"
- Cycle detected: US-002 → US-003 → US-002
Example
Input request: "Create metadata for a user auth feature"
Output:
version: 1
tasks:
- id: AUTH-001
title: Add users table migration
completed: false
dependsOn: []
mutex: ["db-migrations"]
touches: ["db/migrations/**"]
- id: AUTH-002
title: Create auth middleware
completed: false
dependsOn: ["AUTH-001"]
mutex: ["contract:auth-api"]
touches: ["src/auth/**"]
contracts:
produces: ["contract:auth-api"]
consumes: []
Score
Total Score
65/100
Based on repository quality metrics
✓SKILL.md
SKILL.mdファイルが含まれている
+20
○LICENSE
ライセンスが設定されている
0/10
✓説明文
100文字以上の説明がある
+10
○人気
GitHub Stars 100以上
0/15
✓最近の活動
1ヶ月以内に更新
+10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
✓タグ
1つ以上のタグが設定されている
+5
Reviews
💬
Reviews coming soon
