Skill

disc-cases

Use when turning journeys and requests into explicit use cases. Also triggers on 'use case', 'use-case matrix', 'actor trigger action result', or 'main scenarios'.

From pm

Install

Run in your terminal

npx claudepluginhub etusdigital/etus-plugins --plugin pm

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

Hook Development

10 files

Guides implementation of event-driven hooks in Claude Code plugins using prompt-based validation and bash commands for PreToolUse, Stop, and session events.

plugin-dev

83.2k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitMar 25, 2026

Actions

View Source View Plugin View on GitHub View README

Elicitation Entry Rule

BEFORE asking anything in this module:

Read elicitation-state.yaml (at docs/ets/projects/{project-slug}/state/ or knowledge/ template)

Find this module's entry in module_state

If status == "covered" → summarize what exists, ask if user wants to go deeper

If status == "in_progress" → continue from current_probe

If status == "not_started" → start with story probe (see .claude/skills/discovery/knowledge/story-probes.md)

After each question → update elicitation-state.yaml

Use Case Matrix

Elicitation Entry Rule

BEFORE asking anything in this module:

Read elicitation-state.yaml (at docs/ets/projects/{project-slug}/state/ or knowledge/ template)
Find this module's entry in module_state
If status == "covered" → summarize what exists, ask if user wants to go deeper
If status == "in_progress" → continue from current_probe
If status == "not_started" → start with story probe (see .claude/skills/discovery/knowledge/story-probes.md)
After each question → update elicitation-state.yaml

PURPOSE

Convert fuzzy workflows into explicit UC-# entries so that feature briefs, PRDs, user stories, and implementation plans all trace back to observable behavior.

OUTPUT CONTRACT

Every UC-# must include:

actor
trigger
preconditions
action
expected result
visible success criterion
downstream target if known (FB-#, PRD-F-#, US-#)

MINIMUM SCENARIO SET

Try to cover:

main trigger
common repeat action
blocked or invalid start state
one partial-success or fallback scenario when applicable

ANTI-PATTERNS

Do not describe technical implementation here
Do not merge two different triggers into one use case
Do not leave the expected result vague