plan-templates

To generate a .NET implementation plan, provide the feature name and target project mode to produce a ready-to-edit plan.md skeleton. This creates a standardized document outlining domain, application, infrastructure, and API considerations.

A microservice architecture plan should include Constitution Check, Research Findings, Layer Plan, and Dependency Order sections. These sections ensure a reproducible workflow by aligning architecture responsibilities and technical context.

Yes, you can use this plan template generator for both Generic .NET Mode and Microservice Mode. It customizes the plan.md structure based on the selected mode to outline specific architecture considerations.

The best way to structure a plan.md file is to enforce a consistent template with clearly labeled sections for Summary, Technical Context, and Layer Plans. This ensures a reproducible planning workflow across new features.

No, you do not need to manually outline domain and infrastructure layers. The generated template automatically provides sections for domain, application, infrastructure, and API considerations tailored to your project mode.

Your feature planning workflow lacks consistent documentation because it misses a standardized plan.md template. Generating a mode-specific skeleton with predefined sections enforces a reproducible structure for architecture and dependencies.