npx claudepluginhub faysilalshareef/dotnet-ai-kit --plugin dotnet-ai-kitThis skill uses the workspace's default tool permissions.
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.
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.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Generate the plan.md structure based on project mode.
# Implementation Plan: {Feature Name}
**Feature**: {NNN}-{short-name} | **Date**: {DATE} | **Mode**: Generic
**Spec**: spec.md
## Summary
{1-2 sentence overview}
## Constitution Check
Source: `.dotnet-ai-kit/memory/constitution.md`
{PASS/FAIL with notes}
## Technical Context
**Framework**: .NET {version} | **Architecture**: {detected pattern}
**Test Framework**: {detected} | **Key Packages**: {list}
## Research Findings
{Summary of existing patterns from codebase scan}
## Layer Plan
### Domain Layer
- Entities: {list with file paths}
- Value Objects: {list}
- Domain Events: {list}
### Application Layer
- Commands: {list with handlers}
- Queries: {list with handlers}
- Validators: {list}
- Interfaces: {list}
### Infrastructure Layer
- Repositories: {list}
- Services: {list}
- Configurations: {EF configs, DI registrations}
### API Layer
- Endpoints: {list with HTTP methods and paths}
- DTOs: {request/response models}
- Mapping: {profiles or extensions}
## Complexity Tracking
{Only if constitution violations need justification}
plan.md — per-service breakdown:
# Implementation Plan: {Feature Name}
**Feature**: {NNN}-{short-name} | **Date**: {DATE} | **Mode**: Microservice
## Summary
## Constitution Check
Source: `.dotnet-ai-kit/memory/constitution.md`
## Research Findings
## Service Plan
### {domain}-command
- Aggregates: {list}
- Events: {list with data schemas}
- Commands: {list}
### {domain}-query
- Entities: {list}
- Event Handlers: {list}
- Queries: {list}
### {domain}-processor (if applicable)
- Listeners: {list}
- Handlers: {list — what each handler forwards to}
### {domain}-gateway
- Endpoints: {list}
- Proto clients: {list}
### {domain}-controlpanel (if applicable)
- Pages: {list}
- Facades: {list}
## Dependency Order
command → query/processor (parallel) → gateway → controlpanel
service-map.md — Mermaid diagram of service dependencies + per-service change summary.
event-flow.md — Mermaid sequence diagram + event catalogue (name, publisher, subscribers, data schema).
contracts/ — Proto definitions, event schemas for new/updated services.