phuryn/pm-skills

user-stories

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

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/phuryn/pm-skills --skill user-stories

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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
  1. Respect INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
  2. Use plain language a primary school graduate can understand
  3. Link to design files for visual reference
  4. 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

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
phuryn
Communauté

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

Installations / 1h
4
GitHub Stars
28,1 k
Mis à jour
8 nov.
phuryn
Communauté

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

Installations / 1h
2
GitHub Stars
28 k
Mis à jour
8 nov.
phuryn
Communauté

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

Installations / 1h
2
GitHub Stars
28 k
Mis à jour
8 nov.
phuryn
Communauté

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

Installations / 1h
2
GitHub Stars
28 k
Mis à jour
8 nov.