user-story-updater

What This Skill Does

The user-story-updater skill is a specialized automation tool designed for software teams using GitHub to manage their development lifecycle. It systematically refines issue bodies to ensure high-quality, standardized documentation. By parsing raw requirement text, it injects structured, checkable acceptance criteria (ACs) using Markdown syntax and establishes clear connections to parent or child tasks. This skill ensures that every user story is actionable, verifiable, and transparent to the entire engineering team.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-user-story-updater Ensure you have your GitHub repository permissions configured correctly within OpenClaw to allow the agent to read and write to your issue tracker.

Use Cases

• Standardizing Requirements: Convert unstructured notes or loose documentation into clean, GitHub-native issue formats.
• Refining Acceptance Criteria: Automatically transform bullet points into interactive checklist items to facilitate better QA testing and progress tracking.
• Task Mapping: Link existing child tasks or sub-issues to a primary user story to improve project hierarchy and visibility.
• Syncing Specs to Issues: Rapidly update stale issue bodies when project requirements change during the sprint.

Example Prompts

1. "Go to issue #402 and convert the acceptance criteria list into checkable checkboxes, then link it to the backend implementation task #405."
2. "Update the description of user story #122 using the latest technical specs found in the project docs to ensure all ACs are current."
3. "Review issue #88, format the ACs as a task list, and add a section referencing the architectural decision record for this story."

Tips & Limitations

To get the most out of this skill, ensure your initial prompt provides clear source material. While the agent is excellent at formatting, it functions best when requirements are well-defined. Be mindful that this skill modifies live repository data; verify changes in your pull requests or issues after execution. Currently, the skill requires consistent GitHub labels and project structures to successfully map task connections between issues. If your issues are highly complex or nested, provide the specific issue numbers explicitly to prevent the agent from updating the wrong ticket.