user-stories-manager

Manage user stories with status lifecycle and linked artifacts.

1|Updated Jan 8, 2026

Search Tags:#project management #development workflow #feature tracking #agile #user stories #story management

Ready to run

npx skills add https://github.com/JaveedIshaq/ai-workflow-orchestrator --skill user-stories-manager

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-stories-manager
Source: https://github.com/JaveedIshaq/ai-workflow-orchestrator/tree/main/skills/ballee/user-stories-manager
Command: npx skills add https://github.com/JaveedIshaq/ai-workflow-orchestrator --skill user-stories-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured system for managing user stories, ensuring clear tracking of feature development, progress monitoring, and linking of related code artifacts like migrations and tests.

Core Features & Use Cases

Story Management: Create, list, update status, and link resources to user stories.
Workflow Enforcement: Enforces a status lifecycle (draft → in-progress → testing → done) and validates linked artifacts.
Use Case: When starting a new feature, you can create a user story, assign it a priority, and link the database migration and E2E tests as they are developed, ensuring all components are accounted for before marking the story as done.

Quick Start

Use the user-stories-manager skill to create a new story for the 'invoice-system' module.

Frequently Asked Questions about user-stories-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track feature development with linked database migrations and test files?▼

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.

What is the defined status lifecycle for managing agile user stories?▼

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.

How do I enforce acceptance criteria validation before marking a user story as done?▼

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.

Can I use this user story management approach for development team coordination without external dependencies?▼

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.

What's the best way to structure feature tracking for an agile development workflow?▼

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.

Why does a user story fail validation when updating its status to done?▼

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.