arn-spark-use-cases

Orchestrate end-to-end use-case authoring for Arness projects with expert reviews.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-spark-use-cases
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arn-spark-use-cases
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-spark/skills/arn-spark-use-cases
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-spark-use-cases

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates end-to-end use-case authoring for Arness projects by coordinating actor catalogs, use-case drafting, and expert reviews to produce validated artifacts.

Core Features & Use Cases

  • Detect valid Skill Units by verifying SKILL.md at root and ensuring required frontmatter.
  • Coordinate cross-functional expert reviews (business strategist and UX specialist) and merge feedback into a single catalog.
  • Draft use cases in Cockburn format with actor catalogs, relationships, and traceable artifacts.
  • Generate a consolidated use-case index (README) and maintain a living use-cases directory.
  • Support iterative refinement and convergence checks across up to two review rounds.

Quick Start

Run /arn-spark-use-cases to begin identifying valid skill units, drafting use cases, and coordinating expert reviews.

Frequently Asked Questions about arn-spark-use-cases

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write fully-dressed use cases in Cockburn format with cross-domain actors?

Cockburn-style use case authoring structures requirements by defining primary and secondary actors, stakeholder interests, main success scenarios, and extensions. It coordinates actor catalogs and expert reviews to produce validated, fully-dressed use-case artifacts with traceable relationships.

What is the best way to coordinate expert reviews for use-case documentation?

Expert review workflows for use-case documentation route drafts to cross-functional roles like business strategists and UX specialists. Feedback is merged into a single catalog to validate artifacts, supporting iterative refinement across up to two review rounds.

How do I generate a consolidated use-case index and maintain a living directory?

Generating a consolidated use-case index involves creating a README that catalogs all validated use-case artifacts. Maintaining a living use-cases directory requires storing traceable artifacts with annotated relationships to support ongoing project reference.

Does this use-case authoring workflow support iterative refinement and convergence checks?

The use-case authoring workflow supports iterative refinement through structured prompts and convergence checks across up to two review rounds. It ensures feedback from cross-functional expert reviews is fully merged before publishing validated use-case artifacts.

What are the limitations when drafting use cases with cross-domain actor catalogs?

When drafting use cases with cross-domain actor catalogs, convergence checks are capped at two review rounds, limiting iterative depth for highly complex projects. Valid skill units also require a SKILL.md file at the root with proper frontmatter.