user-stories-manager

To track feature development with linked artifacts, you can create a user story, assign it a priority, and link database migrations and E2E tests as they are developed. The system validates these linked artifacts to ensure all components are accounted for before completion.

The defined status lifecycle for managing agile user stories progresses through four stages: draft, in-progress, testing, and done. This workflow is strictly enforced to ensure clear progress monitoring and proper validation of linked artifacts before completion.

You enforce acceptance criteria validation by linking required code artifacts, such as database migrations and test files, to the user story. The system validates story completeness against these acceptance criteria and linked artifacts before allowing the status to advance to done.

Yes, you can use this user story management approach for development team coordination without external dependencies. The skill operates independently using scripts and references to support project management, requiring no additional packages or external tools to function.

The best way to structure feature tracking for an agile workflow is to create user stories with assigned priorities, enforce a status lifecycle from draft to done, and link related code artifacts like migrations and tests to ensure complete feature tracking and progress monitoring.

A user story fails validation when updating to done if it does not meet the defined acceptance criteria or lacks properly linked code artifacts, such as database migrations and test files. The system enforces this lifecycle to prevent incomplete features from being marked as finished.