sm-create-next-story

Create the next development story from epic requirements and architecture documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of the next development story, ensuring it's fully defined with requirements, technical context, and acceptance criteria, ready for implementation.

Core Features & Use Cases

  • Automated Story Generation: Creates new story files based on project progress and epic definitions.
  • Contextual Enrichment: Gathers requirements from epics and technical details from architecture documents.
  • Workflow Integration: Integrates with ClickUp for task tracking and status updates.
  • Use Case: After completing a story, this Skill can automatically identify, define, and prepare the subsequent story, minimizing manual overhead and ensuring continuity in development.

Quick Start

Use the sm-create-next-story skill to prepare the next story in the current epic.

Frequently Asked Questions about sm-create-next-story

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

FAQPage Schema
How do I automatically generate the next development story within an epic?

To automatically generate the next development story, this Skill identifies the subsequent sequential story within an epic, enriches it with requirements from epic files, and adds technical context from architecture documentation. It then creates a story task as a subtask in ClickUp.

How does ClickUp integration work for agile story creation?

ClickUp integration for story creation works by automatically creating the new story task as a subtask of its parent epic. This ensures all necessary metadata and actionable items are included for developer agents directly within your ClickUp workspace.

What do I need to prepare before generating an actionable story?

Before generating an actionable story, you need existing epic files containing requirements and architecture documentation for technical context. The Skill uses these project files to define the story and identify the correct sequential development step within the epic.

Can I use epic management files to create story tasks for developer agents?

Yes, you can use epic management files to create story tasks. The Skill extracts requirements from epic definitions and technical details from architecture documents to fully define the story task for developer agents.

What is the best way to ensure continuity in agile development after completing a story?

The best way to ensure continuity in agile development is to automate the identification and preparation of the subsequent story. This minimizes manual overhead by automatically defining the next actionable story with technical context and acceptance criteria.

Why are my development stories missing technical context and acceptance criteria?

Development stories often miss technical context because manual creation skips referencing architecture documents. This Skill solves the problem by automatically enriching new story files with requirements from epics and technical details from architecture documentation.