update

Update Workflow

You are updating the tracking files for an existing workflow.

Step 1: Identify the Workflow

The workflow name should be provided as $ARGUMENTS. If not provided, list available workflows by scanning .claude/skills/*/context.yaml and ask which one to update.

Read the workflow's files:

• .claude/skills/<name>/context.yaml
• .claude/skills/<name>/tasks.yaml

Present the current status briefly so the user can see what they're working with.

Step 2: Determine What to Update

Ask the user what changed, or infer from the conversation context. Common updates:

Task updates

• Complete a task: set status: done, add completion notes
• Start a task: set status: in-progress, add approach notes
• Block a task: set status: blocked, add blocked_by field
• Add tasks: append new tasks with the next sequential id
• Reorder or remove tasks: adjust as needed

Context updates

• Add learnings: append to learnings list with topic and detail
• Record decisions: append to decisions list with what and why
• Update goal: if the scope has shifted

Step 3: Apply Updates

Edit the YAML files in place using the Edit tool. Preserve existing content — only modify what's changing.

Step 4: Confirm

Show a brief summary of what was changed:

• Tasks updated (with old → new status)
• Learnings or decisions added
• Any other modifications

Rules

• Never overwrite the entire file — use targeted edits
• Keep YAML clean: 2-space indentation, no trailing whitespace
• Task IDs are sequential and never reused — if a task is removed, don't reassign its ID
• Learnings should be specific and include file paths where relevant
• If the user describes work they did in the current conversation, synthesize it into updates rather than asking them to restate