po-manage-story-backlog

Manages a Markdown story backlog tracking follow-ups, technical debt, and optimizations from QA reviews.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill po-manage-story-backlog-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: po-manage-story-backlog
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/product/po-manage-story-backlog
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill po-manage-story-backlog-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Follow-up tasks, technical debt, and optimization opportunities discovered during QA reviews and development often get lost or forgotten. This Skill provides a centralized, structured Markdown backlog to capture, prioritize, track, and archive that deferred work across sprints. ## Core Features & Use Cases - Add Backlog Items: Create uniquely identified items (e.g., [STORY-013-F1]) with type (follow-up, optimization, technical-debt), priority, effort estimates, and success criteria. - Status Lifecycle Management: Move items through TODO, IN_PROGRESS, BLOCKED, DONE, and CANCELLED states with completion metadata. - Review, Report, and Archive: Generate sprint-planning reports grouped by priority, sprint, assignee, or risk, and archive completed items monthly. - Use Case: After a QA review of STORY-013 identifies three follow-ups, the QA agent adds them to docs/STORY-BACKLOG.md, the PO reviews them during sprint planning, and developers update statuses as work completes. ## Quick Start Ask the PO agent to add a high-priority follow-up item from STORY-013 to the story backlog with a title, description, and effort estimate.

Frequently Asked Questions about po-manage-story-backlog

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

FAQPage Schema
How do I add a follow-up item to the story backlog after a QA review?▼

Call the manage-story-backlog operation with the story ID, item type (F for follow-up), priority, title, description, and effort estimate. The skill generates a unique ID like [STORY-013-F1] and inserts the item into the correct priority section of docs/STORY-BACKLOG.md.

How do I track technical debt from development in a backlog?▼

During development, add items with item_type T and source set to Development, including effort estimates and risk levels. The backlog stores them alongside QA follow-ups so the PO can prioritize debt repayment during sprint planning.

Where is the story backlog file stored and can I change it?▼

The backlog defaults to docs/STORY-BACKLOG.md and is configured via the storyBacklogLocation key in core-config.yaml. You can also configure archive location, review schedule, and auto-archive timing in the storyBacklog config section.

What statuses can a backlog item have?▼

Items move through IDEA, TODO, IN_PROGRESS, BLOCKED, DONE, and CANCELLED states. Completed items are marked DONE with completion notes and later moved to a monthly archive file to keep the main backlog clean.

Can I generate backlog reports for sprint planning?▼

Yes, the review operation generates reports grouped by status, priority, sprint, assignee, or risk. It also suggests priority adjustments based on item age, dependencies, deadlines, and team capacity.