removed dead code and obsolete levels 0-4 ref

Author: Brian Madison

docs/_STYLE_GUIDE.md

@@ -6,17 +6,17 @@ This project adheres to the [Google Developer Documentation Style Guide](https:/
 
 ## Project-Specific Rules
 
-| Rule | Specification |
-|------|---------------|
-| No horizontal rules (`---`) | Fragments reading flow |
-| No `####` headers | Use bold text or admonitions instead |
-| No "Related" or "Next:" sections | Sidebar handles navigation |
-| No deeply nested lists | Break into sections instead |
-| No code blocks for non-code | Use admonitions for dialogue examples |
-| No bold paragraphs for callouts | Use admonitions instead |
-| 1-2 admonitions per section max | Tutorials allow 3-4 per major section |
-| Table cells / list items | 1-2 sentences max |
-| Header budget | 8-12 `##` per doc; 2-3 `###` per section |
+| Rule                             | Specification                            |
+| -------------------------------- | ---------------------------------------- |
+| No horizontal rules (`---`)      | Fragments reading flow                   |
+| No `####` headers                | Use bold text or admonitions instead     |
+| No "Related" or "Next:" sections | Sidebar handles navigation               |
+| No deeply nested lists           | Break into sections instead              |
+| No code blocks for non-code      | Use admonitions for dialogue examples    |
+| No bold paragraphs for callouts  | Use admonitions instead                  |
+| 1-2 admonitions per section max  | Tutorials allow 3-4 per major section    |
+| Table cells / list items         | 1-2 sentences max                        |
+| Header budget                    | 8-12 `##` per doc; 2-3 `###` per section |
 
 ## Admonitions (Starlight Syntax)
 
@@ -40,31 +40,31 @@ Critical warnings only — data loss, security issues
 
 ### Standard Uses
 
-| Admonition | Use For |
-|------------|---------|
-| `:::note[Prerequisites]` | Dependencies before starting |
-| `:::tip[Quick Path]` | TL;DR summary at document top |
-| `:::caution[Important]` | Critical caveats |
-| `:::note[Example]` | Command/response examples |
+| Admonition               | Use For                       |
+| ------------------------ | ----------------------------- |
+| `:::note[Prerequisites]` | Dependencies before starting  |
+| `:::tip[Quick Path]`     | TL;DR summary at document top |
+| `:::caution[Important]`  | Critical caveats              |
+| `:::note[Example]`       | Command/response examples     |
 
 ## Standard Table Formats
 
 **Phases:**
 
 ```md
-| Phase | Name | What Happens |
-|-------|------|--------------|
-| 1 | Analysis | Brainstorm, research *(optional)* |
-| 2 | Planning | Requirements — PRD or tech-spec *(required)* |
+| Phase | Name     | What Happens                                 |
+| ----- | -------- | -------------------------------------------- |
+| 1     | Analysis | Brainstorm, research *(optional)*            |
+| 2     | Planning | Requirements — PRD or tech-spec *(required)* |
 ```
 
 **Commands:**
 
 ```md
-| Command | Agent | Purpose |
-|---------|-------|---------|
-| `*workflow-init` | Analyst | Initialize a new project |
-| `*prd` | PM | Create Product Requirements Document |
+| Command      | Agent   | Purpose                              |
+| ------------ | ------- | ------------------------------------ |
+| `brainstorm` | Analyst | Brainstorm a new project             |
+| `prd`        | PM      | Create Product Requirements Document |
 ```
 
 ## Folder Structure Blocks
@@ -141,13 +141,13 @@ your-project/
 
 ### Types
 
-| Type | Example |
-|------|---------|
-| **Index/Landing** | `core-concepts/index.md` |
-| **Concept** | `what-are-agents.md` |
-| **Feature** | `quick-flow.md` |
-| **Philosophy** | `why-solutioning-matters.md` |
-| **FAQ** | `brownfield-faq.md` |
+| Type              | Example                      |
+| ----------------- | ---------------------------- |
+| **Index/Landing** | `core-concepts/index.md`     |
+| **Concept**       | `what-are-agents.md`         |
+| **Feature**       | `quick-flow.md`              |
+| **Philosophy**    | `why-solutioning-matters.md` |
+| **FAQ**           | `brownfield-faq.md`          |
 
 ### General Template
 
@@ -217,14 +217,14 @@ your-project/
 
 ### Types
 
-| Type | Example |
-|------|---------|
-| **Index/Landing** | `workflows/index.md` |
-| **Catalog** | `agents/index.md` |
-| **Deep-Dive** | `document-project.md` |
-| **Configuration** | `core-tasks.md` |
-| **Glossary** | `glossary/index.md` |
-| **Comprehensive** | `bmgd-workflows.md` |
+| Type              | Example               |
+| ----------------- | --------------------- |
+| **Index/Landing** | `workflows/index.md`  |
+| **Catalog**       | `agents/index.md`     |
+| **Deep-Dive**     | `document-project.md` |
+| **Configuration** | `core-tasks.md`       |
+| **Glossary**      | `glossary/index.md`   |
+| **Comprehensive** | `bmgd-workflows.md`   |
 
 ### Reference Index Pages
 
@@ -303,19 +303,19 @@ Starlight generates right-side "On this page" navigation from headers:
 ```md
 ## Category Name
 
-| Term | Definition |
-|------|------------|
-| **Agent** | Specialized AI persona with specific expertise that guides users through workflows. |
+| Term         | Definition                                                                               |
+| ------------ | ---------------------------------------------------------------------------------------- |
+| **Agent**    | Specialized AI persona with specific expertise that guides users through workflows.      |
 | **Workflow** | Multi-step guided process that orchestrates AI agent activities to produce deliverables. |
 ```
 
 ### Definition Rules
 
-| Do | Don't |
-|----|-------|
+| Do                            | Don't                                       |
+| ----------------------------- | ------------------------------------------- |
 | Start with what it IS or DOES | Start with "This is..." or "A [term] is..." |
-| Keep to 1-2 sentences | Write multi-paragraph explanations |
-| Bold term name in cell | Use plain text for terms |
+| Keep to 1-2 sentences         | Write multi-paragraph explanations          |
+| Bold term name in cell        | Use plain text for terms                    |
 
 ### Context Markers
 

docs/explanation/brownfield-faq.md

@@ -11,7 +11,6 @@ Quick answers to common questions about brownfield (existing codebase) developme
   - [Do I have to run document-project for brownfield?](#do-i-have-to-run-document-project-for-brownfield)
   - [What if I forget to run document-project?](#what-if-i-forget-to-run-document-project)
   - [Can I use Quick Spec Flow for brownfield projects?](#can-i-use-quick-spec-flow-for-brownfield-projects)
-  - [How does workflow-init handle old planning docs?](#how-does-workflow-init-handle-old-planning-docs)
   - [What if my existing code doesn't follow best practices?](#what-if-my-existing-code-doesnt-follow-best-practices)
 
 ### What is brownfield vs greenfield?
@@ -44,17 +43,6 @@ Yes! Quick Spec Flow works great for brownfield. It will:
 
 Perfect for bug fixes and small features in existing codebases.
 
-### How does workflow-init handle old planning docs?
-
-workflow-init asks about YOUR current work first, then uses old artifacts as context:
-
-1. Shows what it found (old PRD, epics, etc.)
-2. Asks: "Is this work in progress, previous effort, or proposed work?"
-3. If previous effort: Asks you to describe your NEW work
-4. Determines level based on YOUR work, not old artifacts
-
-This prevents old Level 3 PRDs from forcing Level 3 workflow for a new Level 0 bug fix.
-
 ### What if my existing code doesn't follow best practices?
 
 Quick Spec Flow detects your conventions and asks: "Should I follow these existing conventions?" You decide:

docs/how-to/brownfield/index.md

@@ -36,9 +36,11 @@ Your `docs/` folder should contain succinct, well-organized documentation that a
 
 For complex projects, consider using the `document-project` workflow. It offers runtime variants that will scan your entire project and document its actual current state.
 
-## Step 3: Initialize for Brownfield Work
+## Step 3: Get Help
 
-Run `workflow-init`. It should recognize you are in an existing project. If not, explicitly clarify that this is brownfield development for a new feature.
+Get help to know what to do next based on your unique needs
+
+Run `bmad-help` to get guidance when you are not sure what to do next.
 
 ### Choosing Your Approach
 

src/bmm/workflows/bmad-quick-flow/quick-dev/data/project-levels.yaml

@@ -23,7 +23,7 @@ agent:
     - trigger: list-tasks
       description: Two word trigger
       action: list_tasks
-    - trigger: workflow-init-process
+    - trigger: three-word-process
       description: Three word trigger
       action: init_workflow
     - trigger: test123