feature-spec

To generate an implementation plan from a PRD and feature slice, you provide the slice PRD, architectural guidance, and a reference slice. The system then outputs a plan.md detailing file paths, class names, method signatures, and test coverage steps.

A feature slice in backend architecture planning is a specific product capability requiring translation into executable code. It uses PRD requirements and architectural context to define exact files, C# classes, API endpoints, and tests.

You translate API design and architecture context into file paths and method signatures by processing the slice PRD alongside a reference slice. This yields a concrete plan.md specifying layer-by-layer implementation steps and endpoint contracts.

Yes, this approach works with C# and MediatR patterns for implementation planning. It reads architectural guidance and generates a plan.md with precise C# class names, method signatures, and status codes tailored to your backend structure.

To create a developer-ready execution blueprint for backend work, you need a slice PRD, architectural documents, and a nearby reference slice. This enables the generation of a plan.md with exact endpoint contracts and test coverage.

Your feature slice plan needs a reference slice and architectural guidance to maintain codebase consistency. Reading these existing documents ensures the generated plan.md aligns file paths and class structures with established project patterns.