evo-create-story

Generate a context-rich story file from a workflow specification.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-create-story
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evo-create-story
Source: https://github.com/DavidsonGomes/claude_cowork_workspace/tree/main/.claude/skills/evo-create-story
Command: npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-create-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a contextual story file that contains all necessary information for implementing a story, reducing manual setup.

Core Features & Use Cases

  • Context consolidation: compiles relevant project context into a single story file.
  • Identifier mapping: assigns a story identifier for easy retrieval and reference.
  • Activation-ready: produces a file ready to be loaded by agents.

Quick Start

Provide a story identifier and run the skill to generate and save the new story file with full context.

Frequently Asked Questions about evo-create-story

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

FAQPage Schema
How do I generate a context-rich story file for project implementation?▼

To generate a context-rich story file, you provide a story identifier like 'story-001' and the skill reads the workflow specification from _evo/bmm/workflows/4-implementation/create-story/workflow.md to compile relevant project context into a ready-to-use file.

What is an evo story file and when do I need one?▼

An evo story file is a contextual document containing all necessary information for implementing a story. You need one when starting a new evo story across projects or modules to ensure reproducible context and reduce manual setup.

Does generating a story file require access to the project root?▼

Yes, generating a story file requires access to the project root to read the workflow specification from _evo/bmm/workflows/4-implementation/create-story/workflow.md and output the ready-to-use story file in the designated location.

Can I use this to create implementation stories across different modules?▼

Yes, you can create implementation stories across different modules by providing a unique story identifier for each request, allowing the skill to generate reproducible context files applicable across various projects.

What is the best way to automate context consolidation for implementation stories?▼

The best way to automate context consolidation is running this skill with a story identifier; it automatically compiles relevant project context into a single activation-ready file loadable by agents.