implement-usecase

Orchestrate subagents to implement and review application service use cases.

Updated Feb 27, 2025

Search Tags:#subagents #orchestration #code-review #domain-models #usecase-implementation #spec-usecases

Ready to run

npx skills add https://github.com/tuanemuy/dotfiles --skill implement-usecase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-usecase
Source: https://github.com/tuanemuy/dotfiles/tree/main/config/claude/skills/implement-usecase
Command: npx skills add https://github.com/tuanemuy/dotfiles --skill implement-usecase

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill orchestrates the implementation and review of use cases for application services by coordinating subagents, enabling the main agent to focus on orchestration.

Core Features & Use Cases

Subagent-driven implementation: delegates domain-specific work to specialized agents to ensure adherence to spec.
Integrated review cycle: runs a structured review to validate domain logic and architectural alignment before finalization.
Progress and quality gates: ensures typecheck and lint checks are executed and tracked, updating spec progress.

Quick Start

Start by reading CLAUDE.md at the project root, then initiate the implement-usecase workflow to begin coordinating subagents.

Frequently Asked Questions about implement-usecase

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

FAQPage Schema

How do I orchestrate usecase implementation across multiple subagents?▼

Orchestrate usecase implementation by delegating domain-specific application service tasks to subagents, allowing the main agent to focus on coordination and architectural alignment. This ensures adherence to spec/usecases diagrams while maintaining orchestration control.

Can I enforce typecheck and lint checks during usecase implementation?▼

Yes, the usecase implementation workflow enforces typecheck and lint checks as quality gates. These checks are executed and tracked during subagent coordination, ensuring code quality before finalizing the application service layer implementation.

Why does usecase implementation require spec/usecases and spec/domains?▼

Usecase implementation requires spec/usecases and spec/domains because subagents need defined domain models and usecase diagrams to implement the application service layer correctly. Without these specs, subagents cannot ensure architectural alignment or domain logic accuracy.

What's the best way to track progress during usecase implementation?▼

Track progress by updating spec progress docs during the implementation workflow. The orchestration process updates progress documentation as subagents complete domain-specific work, ensuring visibility into implementation status across the usecase layer.