一键导入
ralph-claim-feature
Atomically claim a feature for a teammate. Uses file locking to prevent two teammates from claiming the same feature. Teams variant only.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Atomically claim a feature for a teammate. Uses file locking to prevent two teammates from claiming the same feature. Teams variant only.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ralph-claim-feature |
| description | Atomically claim a feature for a teammate. Uses file locking to prevent two teammates from claiming the same feature. Teams variant only. |
| user-invocable | false |
Atomically claim the next available feature for a teammate.
In team mode, multiple implementer teammates work in parallel. This command ensures that no two teammates claim the same feature by using file locking around the read-modify-write operation.
in_progress feature (claimed_by matches), return it (retry scenario)pending feature with no claimed_by valuestatus to in_progress, set claimed_by to the teammate name"implementer-1")feature_list.json (default: ./feature_list.json)JSON object of the claimed feature:
{
"id": "F042",
"description": "Validate email format on registration",
"status": "in_progress",
"claimed_by": "implementer-1",
...
}
If no features are available to claim:
{ "result": "ALL_CLAIMED" }
ralph skill claim-feature --teammate "implementer-1"
This command adds one optional field to each feature:
{ "claimed_by": "implementer-1" }
claimed_by persists across session crashes, preventing re-claiming by other teammatesGet a compact summary of project status and feature counts from feature_list.json.
Select the next feature to implement from feature_list.json based on priority rules (in_progress first, then first pending).
Increment the attempts counter for a feature after a failed implementation attempt. Optionally sets the last_error message.
Interactive assistant that guides users through creating high-quality PRDs for Ralph-RLM Framework. Asks structured questions about project type, requirements, testing needs, and dependency ordering.
Update the status of a feature in feature_list.json (pending, in_progress, complete, or blocked) and recalculate stats.
PRD quality checklist that validates feature completeness, test coverage, sizing, dependency ordering, and acceptance criteria quality.