From rhythms
Update, share, or delete Rhythms goals safely. Use when the user wants to rename a goal, change owners or teams, update dates or visibility, share a goal, delegate ownership-related work, or remove a goal.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rhythms:goal-managementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user wants to change existing goals in Rhythms.
Use this skill when the user wants to change existing goals in Rhythms.
Use the current curated goal tools:
get_goalupdate_goalsshare_goalsdelete_goalsDo not update or delete a goal until the target is unambiguous.
If the user provides:
If more than one plausible goal matches, ask the user to clarify before mutating anything.
Use update_goals for changes such as:
Before calling update_goals:
When the user says "add" rather than "replace" for multi-value fields like delegates, labels, teams, or owners, avoid overwriting the current state accidentally. Inspect the current goal first when needed.
Use share_goals when the user wants to give users or teams access to goals.
Before sharing:
If the target user or team is ambiguous, clarify first.
Use delete_goals only after explicit confirmation.
Deletion should be treated as destructive even when the user sounds confident.
Before deleting:
For multi-goal deletes, be especially explicit about scope.
After a successful mutation:
After a failed mutation:
npx claudepluginhub getrhythms/rhythms-claude-plugin --plugin rhythmsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.