uc-new-project

Create structured UseCase drafts with per-step Markdown artifacts and Mermaid diagrams.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/GoGradually/usecase-driven-design-skills --skill uc-new-project
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: uc-new-project
Source: https://github.com/GoGradually/usecase-driven-design-skills/tree/main/usecase-driven-design/skills/uc-new-project
Command: npx skills add https://github.com/GoGradually/usecase-driven-design-skills --skill uc-new-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create structured UseCase drafts for new projects.

Core Features & Use Cases

  • File-based, step-by-step UseCase drafting with per-step Markdown artifacts.
  • Mandatory Mermaid diagrams for visuals and a final integrated draft.
  • Supports BCE analysis, domain modeling, system boundary, and pre/post-conditions across an 8-step workflow.
  • Final consolidation of per-step outputs into a single draft file for review.

Quick Start

Provide the project name and system overview to begin the 8-step workflow and generate step-by-step markdown artifacts.

Frequently Asked Questions about uc-new-project

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

FAQPage Schema
How do I draft a UseCase for a new software project?▼

You can draft a new project UseCase by running an 8-step workflow that generates per-step Markdown artifacts and consolidates them into a final integrated draft with Mermaid diagrams.

What is included in a structured UseCase draft?▼

A structured UseCase draft includes UC lists, scenarios, domain models, state models, BCE analysis, system boundaries, exceptions, conditions, and Mermaid diagrams consolidated from per-step outputs.

How do I generate Mermaid diagrams for system boundaries and domain models?▼

You generate mandatory Mermaid diagrams by progressing through the UseCase workflow steps, which automatically integrate visual diagrams for system boundaries and domain models into the final draft.

Can I use Markdown for step-by-step UseCase development?▼

Yes, you can use Markdown for step-by-step UseCase development because the workflow produces mandatory per-step Markdown artifacts before consolidating them into a single draft file for review.

What do I need to start the 8-step UseCase workflow?▼

To start the 8-step UseCase workflow, you need to provide the project name and system overview, which initializes the generation of step-by-step Markdown artifacts and diagrams.

How does BCE analysis integrate into UseCase design?▼

BCE analysis integrates into UseCase design as a mandatory step within the 8-step workflow, automatically incorporating Boundary-Control-Entity classifications into the final consolidated draft.