Verify code changes against documented AIDD core user stories.
npx skills add https://github.com/GrinRus/ai_driven_dev_v2 --skill user-story-check
Please help me install this Agent Skill. Skill: user-story-check Source: https://github.com/GrinRus/ai_driven_dev_v2/tree/main/.agents/skills/user-story-check Command: npx skills add https://github.com/GrinRus/ai_driven_dev_v2 --skill user-story-check
This Skill eliminates the risk of misalignment between code changes and documented AIDD product intent, preventing scope creep and ensuring all work stays consistent with core user stories without unnecessary documentation overhead.
Use the user-story-check skill to evaluate your proposed AIDD workflow change against core user stories and identify any required documentation updates.
High-intent search queries and answers about installing and using this skill.
To align code changes with documented user stories, you can evaluate proposed modifications against existing core narratives to identify impacted workflows, detect scope changes, and flag mismatches between implementation plans and product intent.
Product documentation requires updates when a proposed code change introduces new product scope rather than pure implementation details, extending or modifying existing user stories and impacting documented workflow semantics.
Detect scope creep in AIDD workflow modifications by verifying proposed changes against documented user stories, distinguishing new product scope from implementation details, and highlighting discrepancies for team review.
User story impact analysis for runtime adapter scope identifies which existing user stories a proposed change supports, extends, or threatens, ensuring modifications remain consistent with documented product goals.
You can check if an implementation plan matches documented product intent by analyzing proposed changes to flag mismatches between code implementation plans and documented product goals, preventing scope creep and misalignment.
Modifying operator user experience requires documentation updates if the change impacts documented workflow semantics, distribution, or evaluation scope, extending existing user stories rather than just adjusting implementation details.
bketelsenGenerate a lightweight Product Requirements Document defining vision, user problems, and success metrics.
Chronote-ggAutomates Git/Markdown-based public documentation creation and updates for software products.
cloudvoyantFetch open pull requests and generate proposed code fixes for unresolved review comments.
PVPhaCreate MVP plans with scope, user stories, acceptance criteria, and task sequencing.
