feat: add custom agents and quick-flow workflows, remove tech-spec track

Major Changes:
- Add sample custom agents demonstrating installable agent system
  - commit-poet: Generates semantic commit messages (BMAD Method repo sample)
  - toolsmith: Development tooling expert with knowledge base covering bundlers, deployment, docs, installers, modules, and tests (BMAD Method repo sample)
  - Both agents demonstrate custom agent architecture and are installable to projects via BMAD installer system
  - Include comprehensive installation guides and sidecar knowledge bases

- Add bmad-quick-flow methodology for rapid development
  - create-tech-spec: Direct technical specification workflow
  - quick-dev: Flexible execution workflow supporting both tech-spec-driven and direct instruction development
  - quick-flow-solo-dev (Barry): 1 man show agent specialized in bmad-quick-flow methodology
  - Comprehensive documentation for quick-flow approach and solo development

- Remove deprecated tech-spec workflow track
  - Delete entire tech-spec workflow directory and templates
  - Remove quick-spec-flow.md documentation (replaced by quick-flow docs)
  - Clean up unused epic and story templates

- Fix custom agent installation across IDE installers
  - Repair antigravity and multiple IDE installers to properly support custom agents
  - Enable custom agent installation via quick installer, agent installer, regular installer, and special agent installer
  - All installation methods now accessible via npx with full documentation

Infrastructure:
- Update BMM module configurations and team setups
- Modify workflow status paths to support quick-flow integration
- Reorganize documentation with new agent and workflow guides
- Add custom/ directory for user customizations
- Update platform codes and installer configurations

src/modules/bmm/workflows/bmad-quick-flow/quick-dev/instructions.md

@@ -0,0 +1,96 @@
+# Quick-Dev - Flexible Development Workflow
+
+<workflow>
+
+<critical>Communicate in {communication_language}, tailored to {user_skill_level}</critical>
+<critical>Execute continuously until COMPLETE - do not stop for milestones</critical>
+<critical>Flexible - handles tech-specs OR direct instructions</critical>
+<critical>ALWAYS respect {project_context} if it exists - it defines project standards</critical>
+
+<checkpoint-handlers>
+  <on-select key="a">Load and execute {advanced_elicitation}, then return</on-select>
+  <on-select key="p">Load and execute {party_mode_workflow}, then return</on-select>
+  <on-select key="t">Load and execute {create_tech_spec_workflow}</on-select>
+</checkpoint-handlers>
+
+<step n="1" goal="Load project context and determine execution mode">
+
+<action>Check if {project_context} exists. If yes, load it - this is your foundational reference for ALL implementation decisions (patterns, conventions, architecture).</action>
+
+<action>Parse user input:
+
+**Mode A: Tech-Spec** - e.g., `quick-dev tech-spec-auth.md`
+→ Load spec, extract tasks/context/AC, goto step 3
+
+**Mode B: Direct Instructions** - e.g., `refactor src/foo.ts...`
+→ Offer planning choice
+</action>
+
+<check if="Mode A">
+  <action>Load tech-spec, extract tasks/context/AC</action>
+  <goto>step_3</goto>
+</check>
+
+<check if="Mode B">
+  <ask>**[t] Plan first** - Create tech-spec then implement
+**[e] Execute directly** - Start now</ask>
+
+  <check if="t">
+    <action>Load and execute {create_tech_spec_workflow}</action>
+    <action>Continue to implementation after spec complete</action>
+  </check>
+
+  <check if="e">
+    <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
+    <goto>step_2</goto>
+  </check>
+</check>
+
+</step>
+
+<step n="2" goal="Quick context gathering (direct mode)">
+
+<action>Identify files to modify, find relevant patterns, note dependencies</action>
+
+<action>Create mental plan: tasks, acceptance criteria, files to touch</action>
+
+</step>
+
+<step n="3" goal="Execute implementation" id="step_3">
+
+<action>For each task:
+
+1. **Load Context** - read files from spec or relevant to change
+2. **Implement** - follow patterns, handle errors, follow conventions
+3. **Test** - write tests, run existing tests, verify AC
+4. **Mark Complete** - check off task [x], continue
+   </action>
+
+<action if="3 failures">HALT and request guidance</action>
+<action if="tests fail">Fix before continuing</action>
+
+<critical>Continue through ALL tasks without stopping</critical>
+
+</step>
+
+<step n="4" goal="Verify and complete">
+
+<action>Verify: all tasks [x], tests passing, AC satisfied, patterns followed</action>
+
+<check if="using tech-spec">
+  <action>Update tech-spec status to "Completed", mark all tasks [x]</action>
+</check>
+
+<output>**Implementation Complete!**
+
+**Summary:** {{implementation_summary}}
+**Files Modified:** {{files_list}}
+**Tests:** {{test_summary}}
+**AC Status:** {{ac_status}}
+</output>
+
+<action>You must explain what was implemented based on {user_skill_level}</action>
+
+</step>
+
+</workflow>