udoc

name	udoc
description	Update documentation and generate changelog after task implementation. Use when asked to 'update docs', 'generate changelog', 'sync documentation with code', or when a task is complete and docs need updating. NOT for creating new product docs (use /product).
argument-hint	["task-path"]

Update Documentation (UDOC)

Announcement: Begin with: "I'm using the udoc skill for documentation update and changelog."

PRIMARY OBJECTIVE

Generate documentation updates and changelog entries from a completed task implementation.

CONTEXT

Use when:

• Task implementation is complete (before or after PR/merge)
• Documentation needs updating to reflect code changes
• Changelog entry needed for the task

WORKFLOW

STEP 1: Resolve Task Path

1. Parse $ARGUMENTS for a task directory path
2. If not provided — Ask: "Which task to update docs for? Provide task directory path (e.g., tasks/task-2026-02-09-feature-name/)." (Don't guess — picking the wrong task would generate a misleading changelog that may end up in the repo history.)
3. Validate: find tech-decomposition-*.md inside the task directory
4. If not found — error with available task directories

STEP 2: Update Docs + Generate Changelog (parallel subagents)

Spawn both subagents in the same turn — they operate on the same task document and do not depend on each other's output:

• docs-updater — "Review the task document at [TASK_DOCUMENT_PATH] and update all relevant documentation files based on the implemented changes. Return a summary of what documentation was updated."
• changelog-generator — "Generate a changelog entry based on the task document at [TASK_DOCUMENT_PATH] covering the main feature implementation. The docs-updater runs in parallel; its updates will be included in the same commit."

Do not default to sequential. When calls have no dependencies, batch them in one turn.

Capture both outputs: the summary of documentation changes and the changelog entry.

STEP 3: Offer Commit (user-gated)

1. Show user what changed:
   • git diff --stat for modified files
   • Brief summary from both agents
2. Ask: "Commit these documentation and changelog updates?" (This skill may run before a PR is opened; the user may want to squash docs into the feature commit rather than create a separate docs commit.)
3. If approved:

   # Stage exactly the files the two subagents reported touching.
   # Do not use `git add -A` (may pull in secrets) and do not assume
   # everything lives under docs/ — changelog-generator writes to
   # docs/changelogs/, but docs-updater may touch README.md,
   # product-docs/, or other locations.
   
   git add <files listed in docs-updater summary> \
           docs/changelogs/YYYY-MM-DD/changelog.md
   git commit -m "docs: update documentation and changelog
   
   - Documentation updates: [DOCS_SUMMARY]
   - Changelog entry: [CHANGELOG_SUMMARY]
   
   Generated by docs-updater and changelog-generator agents."
   

4. If on a feature branch, ask whether to push

STEP 4: Summary

Report to user:

Documentation updated!

**Docs**: [list of updated files]
**Changelog**: docs/changelogs/YYYY-MM-DD/changelog.md
**Committed**: Yes/No

ERROR HANDLING

• Task not found: List available task directories under tasks/
• No changes detected: Inform user, suggest checking if docs are already up to date
• Agent fails: Report which agent failed, suggest running manually

SUCCESS CRITERIA

• Task document found and analyzed
• Documentation updated for affected files
• Changelog entry created under docs/changelogs/YYYY-MM-DD/ using today's date (the date the docs update runs, not the task creation or completion date)
• User informed of all changes
• Changes committed only with user approval