write-a-prd
This skill will be invoked when the user wants to create a PRD. You may skip steps if you don't consider them necessary.
The target stack is .NET (C# / ASP.NET Core) for backend and web UI (Razor Pages, Blazor, or a JS frontend). The scope can be any part of the app: domain classes, interfaces, API endpoints, services, UI components, database schema, etc.
-
Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
-
Explore the repo to verify their assertions and understand the current state of the codebase. Pay attention to:
- Project structure (solution layout, layers: Domain, Application, Infrastructure, Web)
- Existing patterns (CQRS, MediatR, repositories, minimal APIs vs controllers, etc.)
- UI approach (Razor Pages, Blazor, or separate frontend)
- ORM and database (EF Core, Dapper, etc.)
-
Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For .NET web apps, make sure to cover:
- Which layer(s) are affected (domain model, application logic, infrastructure, API, UI)
- Whether new endpoints, pages, or components are needed
- Auth/authorization requirements
- Any schema or migration changes
More from fboucher/skills
grill-me
Interview the user persistently about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
12prd-to-issues
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
10write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
6tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
5edit-video-blog
Write a polished technical blog post from a video transcript and an initial draft. Use when the user provides a transcript and/or draft and wants a finished article suitable for publication.
5improve-codebase
Explore a codebase to find opportunities for architectural improvement, focusing on making the codebase more testable by deepening shallow modules. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more AI-navigable.
5