Results for “user-story”

This skill should be used when the user asks to "start a new story", "initialize a story project", "create a story", "new book", "set up a story", or wants to begin a new fiction writing project from scratch.

Break large user stories or epics into smaller, independently deliverable stories using systematic splitting patterns.

Visualize the user journey by creating a hierarchical map of activities, steps, and tasks to build shared understanding and prioritize features.

Create a six-frame storyboard that shows a user's journey from problem to solution, using a classic narrative arc to build empathy and align stakeholders.

Plans sprints, breaks user stories into tasks, and estimates story points from BA and TechLead artifacts, producing sprint plan, task breakdown, and story point files.

This skill should be used when the user asks to "create a plot arc", "story structure", "add a plot point", "story timeline", "track foreshadowing", "pacing", "act structure", "story arc", "plot outline", or wants to plan and manage the narrative structure of a story.

Breaks applications or features into thin vertical user-story slices with clear acceptance criteria and user-observable value, suitable for backlog planning and feature decomposition.

Generates comprehensive GitHub project plans with Epic > Feature > Story/Enabler > Test hierarchy, dependencies, priorities, and automated issue tracking.

COO planning lead. Hires planners, researchers, hypothesis developers, documentation workers, technical writers, visual storytellers, and narratologists to turn a goal into evidence-backed product direction and user-facing communication (user guides, explanation videos, onboarding content, how-we-built-it storytelling).

Defines when to create Epic, Feature, UserStory, or Task tickets and adds concise guidance to SKILL.md.

Generate user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria, with descriptions, design links, and acceptance criteria.

Create user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

Extract coverage-checked, independently testable MoonSpec user stories from a technical or declarative design and write breakdown output under artifacts/story-breakdowns (gitignored). Use when the user asks to run or reproduce `/moonspec.breakdown`, split a broad design into one-story candidates, preserve source coverage, or build a coverage matrix before `/moonspec.specify`.

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.

Decompose large user stories into thin, independently deliverable vertical slices using the SPIDR method (Spike, Path, Interface, Data, Rules).

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.

Generate data-driven user personas for UX research and product design. Usage: /persona generate [options]

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria, focusing on user situations and outcomes for JTBD-style backlog items.

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.

Write and refine user stories using INVEST criteria, the 'As a X, I want Y, so that Z' format, Gherkin acceptance criteria, definition of ready, anti-patterns, and a review checklist.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.

Creates a consistent minimalist hand-drawn illustrated character from user-provided photos or profile materials, then generates content visuals like knowledge cards, posters, storyboards, and presentation slides featuring that character alongside helper agents.

Manages the full Salesforce user lifecycle: create, deactivate, freeze, assign licenses, configure profiles and roles, set login restrictions, and set up delegated administration.

Manage user journey mapper operations. Auto-activating skill for Visual Content. Triggers on: user journey mapper, user journey mapper Part of the Visual Content skill category. Use when working with user journey mapper functionality. Trigger with phrases like "user journey mapper", "user mapper", "user".

Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".

Write end-user documentation including tutorials, how-to guides, walkthroughs, onboarding flows, and feature documentation. Use when creating documentation for non-technical or semi-technical end users. Also trigger for 'user guide', 'tutorial', 'how-to', 'walkthrough', 'onboarding docs', 'help article', 'user manual', or 'getting started guide'.

Generate user-facing App Store release notes by collecting and summarizing user-impacting changes from git history since the last tag.

Create detailed, actionable user personas from research data, capturing jobs-to-be-done, pain points, desired gains, and unexpected behavioral insights to guide product decisions.

Agent skill for user-tools - invoke with $agent-user-tools