Skip to content
cccskills
FreePublished on GitHub

user-stories

Turn a new feature into user stories: short descriptions of what people need and why. Each story includes a design reference and testable acceptance criteria, with scope intended to fit within one sprint.

OriginalShow the original description

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.

Works withFigma
See how to install

Good for

  • Breaking a new feature into backlog items
  • Defining testable acceptance criteria
  • Sharing user needs alongside design references
  • Sizing stories for a single sprint

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

User Stories

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

Use when: Writing user stories, breaking down features into stories, creating backlog items, or defining acceptance criteria.

Arguments:

  • $PRODUCT: The product or system name
  • $FEATURE: The new feature to break into stories
  • $DESIGN: Link to design files (Figma, Miro, etc.)
  • $ASSUMPTIONS: Key assumptions or context

Step-by-Step Process

  1. Analyze the feature based on provided design and context
  2. Identify user roles and distinct user journeys
  3. Apply 3 C's framework:
    • Card: Simple title and one-liner
    • Conversation: Detailed discussion of intent
    • Confirmation: Clear acceptance criteria
  4. Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
  5. Use plain language a primary school graduate can understand
  6. Link to design files for visual reference
  7. Output user stories in structured format

Story Template

Title: [Feature name]

Description: As a [user role], I want to [action], so that [benefit].

Design: [Link to design files]

Acceptance Criteria:

  1. [Clear, testable criterion]
  2. [Observable behavior]
  3. [System validates correctly]
  4. [Edge case handling]
  5. [Performance or accessibility consideration]
  6. [Integration point]

Example User Story

Title: Recently Viewed Section

Description: As an Online Shopper, I want to see a 'Recently viewed' section on the product page to easily revisit items I considered.

Design: [Figma link]

Acceptance Criteria:

  1. The 'Recently viewed' section is displayed at the bottom of the product page for every user who has previously viewed at least 1 product.
  2. It is not displayed for users visiting the first product page of their session.
  3. The current product itself is excluded from the displayed items.
  4. The section showcases product cards or thumbnails with images, titles, and prices.
  5. Each product card indicates when it was viewed (e.g., 'Viewed 5 minutes ago').
  6. Clicking on a product card leads the user to the corresponding product page.

Output Deliverables

  • Complete set of user stories for the feature
  • Each story includes title, description, design link, and 4-6 acceptance criteria
  • Stories are independent and can be developed in any order
  • Stories are sized for one sprint cycle
  • Stories reference related design documentation

Further Reading

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ab-test-analysis

FreeSummary

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills27.3KUpdated Oct 16, 2026

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills27.3KUpdated Oct 16, 2026

ansoff-matrix

FreeSummary

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills27.3KUpdated Oct 16, 2026

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills27.3KUpdated Oct 16, 2026

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills27.3KUpdated Oct 16, 2026

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills27.3KUpdated Oct 16, 2026

See all skills by phuryn

Report a problem with this skill