skills.rest
GDSDN
GDSDNCOMMUNITY
Explore all skills by this author →
GitHub

po-close-story

Close product development stories by updating status, changelog, and epic indexes.

3|Updated Feb 7, 2026
Search Tags:#changelog#project management#workflow automation#agile#epic tracking#story closure
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill po-close-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: po-close-story
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/product/po-close-story
Command: npx skills add https://github.com/GDSDN/kord-aios --skill po-close-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the final steps of a story's lifecycle, ensuring project documentation and tracking are up-to-date after development is complete.

Core Features & Use Cases

  • Story Closure: Marks a story as 'Done' with references to merge commits or PRs.
  • Project Tracking: Updates epic indexes, backlog counts, and suggests the next story.
  • Use Case: After a feature is merged into the main branch, use this skill to automatically update the story's status to 'Done', add an entry to the changelog, and update the progress of its parent epic.

Quick Start

Use the po-close-story skill to close the story located at 'epics/epic-1/story-1.md' with PR number 123.

Frequently Asked Questions about po-close-story

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

FAQPage Schema
How do I automate story closure and update epic tracking after a merge?▼

Automating story closure updates story status to 'Done' with merge information, adds changelog entries, and synchronizes progress across epic indexes and backlog statistics. This ensures project documentation and tracking remain up-to-date after development is complete.

What is the best way to add changelog entries when closing a project story?▼

The best way to add changelog entries during story closure is to reference the specific pull request or merge commit. The skill integrates this merge information directly into the changelog while marking the story status as 'Done'.

How do I mark a story as Done and get suggestions for the next story?▼

To mark a story as Done and get next story suggestions, you provide the story file path and PR number. The skill updates the status, recalculates backlog counts, and suggests the next story or epic completion for seamless workflow transition.

Does this story closure workflow update backlog statistics automatically?▼

Yes, the story closure workflow automatically updates backlog statistics. It synchronizes progress across epic indexes and backlog counts, ensuring that all project tracking data reflects the newly closed story without requiring manual updates.

Can I use this workflow automation for agile epic tracking without external dependencies?▼

Yes, you can use this agile epic tracking workflow without external dependencies. It operates independently using scripts to update epic indexes, close stories, and manage project status transitions based solely on your local project files.

Related Skills

Explore More Product & Management Skills→
CarlosQ96CarlosQ96

qa-plan

Generate structured QA plans from GDDs and story files.

Community
Advanced
CarlosQ96CarlosQ96

story-done

Verify acceptance criteria, design compliance, and test coverage for game development sprint stories.

Community
Advanced
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
MarcoAntoliniMarcoAntolini
1

update-changelog

Synchronize project changelogs with Git commits and prepare releases.

Community
Intermediate