@codihaus/claude-skills 1.6.21 → 1.6.22

package/skills/debrief/references/use-case-template.md

@@ -1,141 +0,0 @@
-# Use Case Template
-
-Standard template for use case files.
-
-## File Naming
-
-Format: `UC-{GROUP}-{NNN}-{slug}.md`
-
-Examples:
-- `UC-PAY-001-checkout.md`
-- `UC-AUTH-002-password-reset.md`
-
-## Template
-
-```markdown
-# UC-{GROUP}-{NNN}: {Title}
-
-> **Feature**: [[feature-{name}]]
-> **Related**: [[uc-xxx-nnn]], [[uc-xxx-nnn]]
-> **Priority**: Must | Should | Could
-> **Status**: Draft | Confirmed | Updated
-
-## User Story
-
-As a {role},
-I want {goal},
-so that {benefit}.
-
-## Acceptance Criteria
-
-- [ ] Given {precondition}, when {action}, then {expected result}
-- [ ] Given {precondition}, when {action}, then {expected result}
-- [ ] Given {precondition}, when {action}, then {expected result}
-
-## Business Rules
-
-- {Rule 1: condition → outcome}
-- {Rule 2: condition → outcome}
-
-## Edge Cases
-
-| Scenario | Expected Behavior |
-|----------|-------------------|
-| {Edge case 1} | {How to handle} |
-| {Edge case 2} | {How to handle} |
-
-## Open Questions
-
-- [ ] {Question requiring stakeholder input}
-- [ ] {Question for engineering to answer}
-
-## References
-
-- [{Relevant doc}]({url})
-- [{Related example}]({url})
-```
-
-## Priority Levels
-
-| Priority | Meaning | Scope Tier |
-|----------|---------|------------|
-| **Must** | Core functionality, cannot launch without | Core |
-| **Should** | Expected by users, standard feature | Standard |
-| **Could** | Nice to have, differentiator | Full |
-
-## Status Values
-
-| Status | Meaning |
-|--------|---------|
-| **Draft** | Initial version, needs review |
-| **Confirmed** | Stakeholder approved |
-| **Updated** | Changed after initial confirmation |
-
-## Writing Tips
-
-### User Stories
-- Keep role specific: "As a **paying customer**" not "As a user"
-- Goal should be concrete: "change my subscription plan"
-- Benefit explains the "why"
-
-### Acceptance Criteria
-- Use Given/When/Then format
-- Each criterion is independently testable
-- Cover happy path + key error paths
-
-### Business Rules
-- Rules that constrain behavior
-- Not implementation details
-- "Users cannot downgrade during trial period"
-
-### Open Questions
-- Mark with `[ ]` so they can be checked off
-- Tag who needs to answer: "(Stakeholder)" or "(Engineering)"
-
-## Example
-
-```markdown
-# UC-PAY-001: Checkout
-
-> **Feature**: [[feature-billing]]
-> **Related**: [[uc-pay-002]], [[uc-cart-001]]
-> **Priority**: Must
-> **Status**: Draft
-
-## User Story
-
-As a customer with items in cart,
-I want to complete my purchase,
-so that I receive my order.
-
-## Acceptance Criteria
-
-- [ ] Given valid cart, when I click checkout, then I see payment form
-- [ ] Given payment details, when I submit, then payment is processed
-- [ ] Given successful payment, when complete, then I see confirmation
-- [ ] Given failed payment, when error occurs, then I see clear error message
-
-## Business Rules
-
-- Minimum order value: $10
-- Maximum items per order: 50
-- Payment must complete within 30 minutes of cart creation
-
-## Edge Cases
-
-| Scenario | Expected Behavior |
-|----------|-------------------|
-| Cart expires during checkout | Show message, redirect to cart |
-| Item goes out of stock | Remove item, notify user |
-| Network error during payment | Retry option, no duplicate charge |
-
-## Open Questions
-
-- [ ] (Stakeholder) Do we support guest checkout?
-- [ ] (Engineering) Which payment processor to use?
-
-## References
-
-- [Stripe Checkout](https://stripe.com/docs/checkout)
-- [Baymard Checkout UX](https://baymard.com/checkout-usability)
-```