gds-create-story

Generate a dev story file from epics, architecture, and project context.

1|Updated Aug 3, 2025

Search Tags:#workflow #architecture #epics #guardrails #story-generation #dev-story

Ready to run

npx skills add https://github.com/MazenMrad/Obsidio --skill gds-create-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gds-create-story
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/gds-create-story
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill gds-create-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates a ready-to-use, context-rich story file that guides developers to implement a feature end-to-end with guardrails and cross-artifact context.

Core Features & Use Cases

Automated story generation: Produces a complete story file from epics, architecture, and project context, ready for dev-story execution.
Contextual completeness: Embeds previous story learnings, architecture constraints, and project rules to prevent duplication or misalignment.
Guided handoff: Provides a structured dev-agent-ready template and guardrails for flawless implementation.

Quick Start

Run the gds-create-story workflow to generate a comprehensive story file for the selected epic/story.

Frequently Asked Questions about gds-create-story

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

FAQPage Schema

How do I auto-generate a developer story from epics and architecture context?▼

To auto-generate a developer story, run the workflow to aggregate epics, architecture, and project context into a production-ready story file. This file embeds prior learnings and validation signals to guide implementation end-to-end with guardrails for cross-story coherence.

What is a production-ready dev story file?▼

A production-ready dev story file is a comprehensive artifact that contextualizes feature development by embedding architecture constraints, project rules, and previous learnings. It provides a structured template and guardrails for flawless, dev-agent-ready implementation.

How do I maintain cross-story coherence during feature development?▼

Maintain cross-story coherence by embedding prior learnings and validation signals from your project context directly into newly generated story files. This ensures each story aligns with existing architecture constraints and prevents duplication or misalignment.

Can I use automated story generation for end-to-end feature workflows?▼

Yes, automated story generation applies to end-to-end feature development workflows requiring consistent developer guidance. It aggregates project context to produce a ready-to-use story file that guides implementation from start to finish.

Does story generation work without explicit architecture guardrails?▼

Story generation aggregates available architecture and project context to build guardrails automatically. If architecture constraints are missing from the input, the generated story file will lack the necessary validation signals and structured guidance for flawless implementation.