Results for “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.

Reads BA and TechLead artifacts to produce a sprint plan, task breakdown, and story point estimates, creating one tracked todo per sprint task for live pipeline tracking.

Write a roadmap narrative that connects customer problems, company goals, bets, and sequencing.

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.

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

Analyzes an app from video, screenshots, or description, then generates implementation stories in dependency order.

Plan a sprint by estimating team capacity, selecting and sequencing stories, and identifying risks.

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.

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

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 user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

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

Writes user-focused acceptance criteria for Jira stories using Given/When/Then scenarios, and updates the ticket via the Atlassian MCP server.

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.

Chains /mvp and /backend-spec to analyze an app from video, screenshots, or description, then generate implementation stories from the analysis.

Trigger: press release, PM memo, PRD memo, product launch narrative, launch story. Scope: Writing press releases and future launch stories for project alignment. Boundary: Excludes writing functional code or task tracking.

This skill should be used when implementing features from a PRD spec, tracking implementation progress, or resuming work across sessions. Covers Dex task management for PRD story execution, daily workflows, and skill auto-loading.

Turn account data into a QBR that earns the renewal. It builds the value-delivered story, adoption against the goals they signed up for, the open risks stated plainly, the forward roadmap, and the expansion ask, then hands you a deck outline. Built for B2B customer success teams, customizable to your CRM and product analytics. Trigger on "build a QBR", "prep the business review", "quarterly review for this account", "what do I show the customer", "value story for the renewal", or any account-review prep.

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday.

Writes or updates pathway pages for Alan Hirsch's platform, following a 12-section architecture that grounds frameworks in Scripture and story, offers practices, and invites course-based formation.

This skill should be used when the user asks to "plan a feature", "create PRD", "interview me about requirements", "define stories", "write a spec", "break down feature into tasks", "create implementation plan", "help me scope this feature", "what questions should I answer", or discusses feature planning. Covers the PRD interview process, spec structure, story atomization, and 4-phase workflow from idea to Dex tasks.

Review an open GitHub issue for a selected repository against the current codebase, then either close it as already implemented with an evidence comment, label it needs clarification with an explanatory comment, or create a fleshed-out Jira story in the requested board/project when the remaining work is clear. Use when triaging GitHub issues into Jira backlog work or closing stale implemented GitHub issues.