// Process an Anthropic Claude Code release or documentation change and determine its impact on StoryForge. Use when a new Claude Code version is released or docs change.
| name | release-adapt |
| description | Process an Anthropic Claude Code release or documentation change and determine its impact on StoryForge. Use when a new Claude Code version is released or docs change. |
| argument-hint | release-version-or-url |
| disable-model-invocation | true |
Process an Anthropic Claude Code update and determine its impact on StoryForge.
Identify the release or change to evaluate:
Use the upstream-watch agent to check the relevant documentation pages
For each change found, classify the impact:
| Impact Level | Meaning | Action Required |
|---|---|---|
| No Impact | Change doesn't affect StoryForge | Update doc-index.md verified date |
| Docs Impact | Documentation needs updating | Update relevant StoryForge docs |
| Config Impact | Settings or configuration affected | Update settings.json templates |
| Agent Impact | Agent behavior or format affected | Update agent definitions |
| Hook Impact | Hook events or format changed | Update hook configurations |
| Skill Impact | Skill format or behavior changed | Update skill definitions |
| Migration Required | Breaking change needs migration | Create migration Story |
## Upstream Change: (Description)
- Source: (URL or release notes reference)
- Checked: (Today's date)
- Impact: (Classification from table)
- Impacted Files: (List of StoryForge files affected)
- Migration Notes: (What needs to change)
- Validation: (How to verify the adaptation)
- Status: Pending | In Progress | Complete
Save the record to docs/upstream/ or update docs/upstream/release-watch.md
If migration is required:
story-write skillUpdate docs/upstream/doc-index.md with new verification dates
Update docs/anthropic-source-map.md if capability classifications changed
Display the StoryForge Kanban dashboard showing board status, features, active stories, sprint progress, and recent activity. Use to get a quick overview of project delivery state.
Update StoryForge delivery artifacts after work is completed. Updates story status, board, changelog, and captures follow-ups. Use after completing implementation work.
Plan or review a sprint by selecting Stories from Ready state into the sprint backlog. Use for sprint planning or mid-sprint reviews.
Create a new Story with structured fields including acceptance criteria, non-goals, risks, and follow-ups. Use when a new piece of work needs to be planned before implementation.
Link a StoryForge story to a GitHub Issue or Pull Request. Updates the story's GitHub field and optionally adds a comment on the GitHub issue. Use when starting work that relates to a GitHub issue.
Initialize a project with StoryForge Kanban delivery structure. Creates .kanban/ directory with board, backlog, sprint, decisions, changelog, and stories directory. Use when setting up a new project for StoryForge delivery tracking.