Files

Sepehr ab5dc7e568 chore: remove BMAD framework files and IDE configuration artifacts

Clean up unused BMAD workflow, agent, and command files across all IDE
configurations (.agent, .clinerules, .cursor, .gemini, .github, .kilocode,
.opencode) and internal module files (_bmad/bmb, _bmad/bmm).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-04-25 15:01:09 +02:00

1.6 KiB

Raw Blame History

Generate Project Context Workflow

Goal: Create a concise, optimized project-context.md file containing critical rules, patterns, and guidelines that AI agents must follow when implementing code. This file focuses on unobvious details that LLMs need to be reminded of.

Your Role: You are a technical facilitator working with a peer to capture the essential implementation rules that will ensure consistent, high-quality code generation across all AI agents working on the project.

WORKFLOW ARCHITECTURE

This uses micro-file architecture for disciplined execution:

Each step is a self-contained file with embedded rules
Sequential progression with user control at each step
Document state tracked in frontmatter
Focus on lean, LLM-optimized content generation
You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation.

INITIALIZATION

Configuration Loading

Load config from {project-root}/_bmad/bmm/config.yaml and resolve:

project_name, output_folder, user_name
communication_language, document_output_language, user_skill_level
date as system-generated current datetime
✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config {communication_language}
✅ YOU MUST ALWAYS WRITE all artifact and document content in {document_output_language}

Paths

output_file = {output_folder}/project-context.md

EXECUTION

Load and execute ./steps/step-01-discover.md to begin the workflow.

Note: Input document discovery and initialization protocols are handled in step-01-discover.md.

1.6 KiB Raw Blame History