Skill

Create Story

Create a story document, standalone or linked to a design

Install

npx claudepluginhub urso/claudev --plugin blueprint

Tool Access

This skill is limited to using the following tools:

ReadWriteEditGlobGrepBashAskUserQuestion

Preview

Create a story document for a unit of implementable work. Can be standalone or linked to a parent design.

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 26, 2026

Actions

View Source View Plugin View on GitHub View README

Create Story

Create a story document for a unit of implementable work. Can be standalone or linked to a parent design.

Variables

DISCOVERY_GUIDE: ${CLAUDE_PLUGIN_ROOT}/resources/discovery.md
STORY_OPS: ${CLAUDE_PLUGIN_ROOT}/resources/story-operations.md
QUERY_STORIES: ${CLAUDE_PLUGIN_ROOT}/scripts/query-stories.sh
LIST_WORKFLOWS: ${CLAUDE_PLUGIN_ROOT}/scripts/list-workflows.sh

User Input

$ARGUMENTS

Parse for:

--design <id> — link to a parent design
Or: description of the work for a standalone story

Pre-computed Context

Story Workflows

!bash ${CLAUDE_PLUGIN_ROOT}/scripts/list-workflows.sh "" story

Process

1. Load Guides

Read DISCOVERY_GUIDE and STORY_OPS for available tools and procedures.

Read the workflow files listed in the pre-computed context above for story guidelines.

2. Determine Design Link

If --design provided:

Locate and read the design for context
Show existing stories for this design:
```
bash QUERY_STORIES --design <id>
```
This helps the user see what's already covered and what gaps remain.

If no design specified:

Ask user if this story should be linked to a design
If yes, list designs and let user choose
If no, proceed as standalone

3. Gather Story Details

Ask clarifying questions:

What: What work does this story cover?
Tasks: What are the concrete tasks and sub-tasks?
Dependencies: Does this story depend on other stories?

Get user confirmation before proceeding.

4. Determine Story Name

Ask user for a short kebab-case name (e.g., auth-middleware, test-suite).

5. Create Story

Follow the procedures in STORY_OPS to create the story:

Generate ID, write the document, set dependencies
Link to design if applicable

6. Confirm

Report successful creation
Suggest next steps: /develop-story to start implementation

Guidelines

Each story must have at least one ## Tasks section with - [ ] checkboxes
Keep stories small enough to implement in one session where possible
Use status: ready if the story can be worked on now, draft if it needs refinement
When linked to a design, reference the design's approach in Technical Notes