Existing Documentation Inventory
Date: 2026-03-11T11:59:39Z
Summary
The project has a small set of directly relevant documentation files plus BMAD framework support files. For brownfield understanding, the highest-priority sources are the project README and a small number of repo-specific instruction files.
Priority Documentation for Project Understanding
README.md
- Type: readme
- Path:
/workspace/MVC-Starter/README.md
- Scope: whole project
- Notes: Documents IIS setup, project structure, generator workflow, and baseline runtime requirements.
.github/copilot-instructions.md
- Type: project instructions
- Path:
/workspace/MVC-Starter/.github/copilot-instructions.md
- Scope: whole project
- Notes: Documents BMAD runtime conventions, config locations, workflow engine usage, and agent/runtime structure.
_bmad-output/project-context.md
- Type: generated ai-project-context
- Path:
/workspace/MVC-Starter/_bmad-output/project-context.md
- Scope: whole project
- Notes: Derivative documentation generated from workflow analysis. Useful for AI implementation rules, but not an original source of project design intent.
BMAD Framework Documentation Assets
.github/agents/*.md and .github/prompts/*.md provide BMAD agent and prompt definitions.
_bmad/ contains the installed BMAD framework, workflows, templates, and configuration.
- These files are important for maintaining the BMAD layer, but they are secondary to the application docs when documenting the MVC starter itself.
Generated Documentation in This Workflow Run
- Files created under
docs/ by this workflow should be treated as generated brownfield documentation outputs, not original project-authored documents.
Observations
- No dedicated architecture, deployment, API, or data-model markdown docs existed for the application before this workflow run.
- The README is the main human-authored source of project usage and structure.
- Most other markdown assets in the repo belong to the BMAD toolchain rather than the Classic ASP application itself.