skills.rest
SynkraAI
SynkraAIOFFICIAL
Explore all skills by this author →
GitHub

aiox-close-story

Finalizes bookkeeping for QA-completed stories without changing lifecycle status.

3.1k|952|Updated Dec 9, 2025
Search Tags:#bookkeeping#product owner#agile workflow#story closure#AIOX#Quality gates#epic backlog
One-click install
npx skills add https://github.com/SynkraAI/aios-core --skill aiox-close-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aiox-close-story
Source: https://github.com/SynkraAI/aios-core/tree/main/.grok/skills/aiox-close-story
Command: npx skills add https://github.com/SynkraAI/aios-core --skill aiox-close-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After QA marks a story as Done, teams still need consistent administrative closure—updating epic indexes, backlogs, and closure metadata—without risking accidental lifecycle status changes or premature closes.

Core Features & Use Cases

  • Gate-Verified Closure: Blocks any administrative write unless a review verdict exists (PASS, CONCERNS, or WAIVED), acceptance criteria are met, tasks are complete, and quality gates are green.
  • Status Preservation: Guarantees the story's Status remains Done on disk; any other status triggers a halt as an integrity violation.
  • Epic Index Updates: Updates the epic index and backlog with closure metadata and suggests the next story when applicable.
  • Use Case: A product owner finishes a sprint and needs to close out five QA-approved stories, updating the epic index and backlog consistently while ensuring no story is closed without a valid review verdict.

Quick Start

Invoke the close-story workflow with the story file path, for example by asking the agent to close the story at docs/stories/3.2.story.md in interactive mode.

Frequently Asked Questions about aiox-close-story

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

FAQPage Schema
How do I close a completed story in AIOX?▼

Invoke the close-story workflow with the story file path and an optional mode (yolo or interactive). The skill runs the po-close-story task, verifies all pre-close gates, and updates the epic index and backlog while preserving Status: Done.

What happens if a story is not marked Done before closing?▼

The skill halts immediately with no administrative write and no status change. Closing a story in any status other than Done is treated as an integrity violation, since only QA may set the Done status.

Can close-story change a story's lifecycle status?▼

No. The skill never modifies lifecycle status; it only performs administrative bookkeeping such as closure metadata and epic index updates. Status transitions remain the responsibility of QA and other lifecycle workflows.

What review verdicts allow a story to be closed?▼

A story can be closed when the review gate verdict is PASS, CONCERNS (accepted), or WAIVED. A FAIL verdict or a missing verdict blocks closure and causes the workflow to halt.

Why does close-story halt even when the story looks complete?▼

Halts occur when any blocking gate fails: missing review verdict, unmet acceptance criteria, incomplete tasks, missing File List, or red quality gates without a documented waiver. Resolve the failing gate, then rerun the closure.

Related Skills

Explore More Product & Management Skills→
cbbkrd-techcbbkrd-tech

ln-500-story-quality-gate

Orchestrate multi-stage quality gates for software development stories.

Community
Advanced
davila7davila7
30.5k

agile-product-owner

Generates INVEST-compliant user stories and sprint plans from epic definitions.

Community
Intermediate
cassioalexandrecassioalexandre
2

bmad-agent-dev

Execute approved story tasks in strict sequence with passing unit tests.

Community
Advanced
0xtaoist0xtaoist

ln-400-story-executor

Orchestrate Linear or File Story workflows with prioritized task delegation and inline review.

Community
Advanced