Skip to content
Back to skills

Invest Stories

ASecurity

When writing, reviewing, or validating user stories. Used by ARCHITECT-AGENT and PRODUCT-OWNER.

  • 666 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added February 9, 2026
developmentgoreactapidatabase

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill invest-stories --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Invest Stories?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Invest Stories
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-invest-stories/badge)](https://www.skillsdirectory.com/skills/majiayu000-invest-stories)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: invest-stories
description: When writing, reviewing, or validating user stories. Used by ARCHITECT-AGENT and PRODUCT-OWNER.
version: 1.0.0
tokens: ~400
confidence: high
sources:
  - https://www.agilealliance.org/glossary/invest/
  - https://xp123.com/articles/invest-in-good-stories-and-smart-tasks/
last_validated: 2025-01-10
next_review: 2025-01-24
tags: [agile, stories, planning, product]
---

## When to Use
When writing, reviewing, or validating user stories. Used by ARCHITECT-AGENT and PRODUCT-OWNER.

## Patterns

### INVEST Criteria

**I - Independent**
```
✅ Can be developed without waiting for other stories
✅ No circular dependencies
❌ "This needs Story X which needs this"
```

**N - Negotiable**
```
✅ HOW is flexible (implementation not prescribed)
✅ WHAT is clear (outcome defined)
❌ "Must use React Query with exact caching config"
```

**V - Valuable**
```
✅ Delivers value to USER or BUSINESS
✅ Value stated explicitly
❌ "Refactor database layer" (no user value)
✅ "User sees data faster because we optimized queries"
```

**E - Estimable**
```
✅ Team can estimate complexity (S/M/L)
✅ No major unknowns blocking estimation
❌ "Integrate with external API" (which API? what ops?)
```

**S - Small**
```
✅ Completable in 1-3 sessions
✅ Can be code reviewed in one sitting
❌ 10+ acceptance criteria, multiple components
```

**T - Testable**
```
✅ ALL acceptance criteria verifiable
✅ Given/When/Then format used
❌ "System should handle errors gracefully"
✅ "Given invalid input, Then error message X displays"
```

## Anti-Patterns
- Technical stories without user value
- Epic disguised as story (too big)
- Vague AC ("properly handles", "works correctly")
- Implementation prescribed in story
- Circular dependencies between stories

## Verification Checklist
- [ ] Story traces to PRD requirement
- [ ] Each INVEST criterion passes
- [ ] AC uses Given/When/Then
- [ ] No vague words in AC
- [ ] Dependencies are one-way only
- [ ] Estimated as S, M, or L

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.