@zeyue0329/xiaoma-cli 1.0.8 → 1.0.9

package/expansion-packs/bmad-creative-writing/workflows/series-planning.yaml

@@ -0,0 +1,78 @@
+# <!-- Powered by BMAD™ Core -->
+# workflows/series-planning.yaml
+name: series-planning
+title: Series Planning Workflow
+description: |
+  Plan a multi‑book or multi‑season narrative series, including overarching arcs
+  and individual installment roadmaps.
+
+triggers:
+  - command: /series-plan
+  - intent: "plan a series"
+
+inputs:
+  - series_title
+  - genre
+  - num_installments
+
+agents:
+  - plot-architect
+  - world-builder
+  - character-psychologist
+  - narrative-designer
+  - genre-specialist
+  - editor
+
+steps:
+  - id: high_concept
+    title: Define series high concept
+    agent: plot-architect
+    outputs: high_concept
+
+  - id: world_bible
+    title: Build series bible (world, rules, tone)
+    agent: world-builder
+    inputs: high_concept
+    outputs: series_bible
+
+  - id: character_arcs
+    title: Map long‑arc character development
+    agent: character-psychologist
+    inputs:
+      - high_concept
+      - series_bible
+    outputs: character_arc_map
+
+  - id: installment_overviews
+    title: Plot each installment overview
+    agent: plot-architect
+    repeat: num_installments
+    inputs:
+      - high_concept
+      - character_arc_map
+    outputs: installment_overviews
+
+  - id: genre_alignment
+    title: Genre & market alignment check
+    agent: genre-specialist
+    inputs: installment_overviews
+    outputs: market_positioning
+
+  - id: roadmap
+    title: Compile master roadmap
+    agent: narrative-designer
+    inputs:
+      - series_bible
+      - character_arc_map
+      - installment_overviews
+      - market_positioning
+    outputs: series_roadmap
+
+  - id: editorial_review
+    title: Editorial review
+    agent: editor
+    inputs: series_roadmap
+    outputs: final_series_plan
+
+outputs:
+  - final_series_plan

package/expansion-packs/bmad-creative-writing/workflows/short-story-creation.yaml

@@ -0,0 +1,64 @@
+# <!-- Powered by BMAD™ Core -->
+# workflows/short-story-creation.yaml
+name: short-story-creation
+title: Short Story Creation Workflow
+description: |
+  Pipeline for drafting and polishing a standalone short story (up to ~7,500 words).
+
+triggers:
+  - command: /short-story
+  - intent: "write a short story"
+
+inputs:
+  - working_title
+  - genre
+  - target_word_count
+
+agents:
+  - plot-architect
+  - character-psychologist
+  - genre-specialist
+  - narrative-designer
+  - editor
+  - beta-reader
+
+steps:
+  - id: premise
+    title: Generate premise
+    agent: plot-architect
+    outputs: premise
+
+  - id: outline
+    title: Create compact outline
+    agent: plot-architect
+    inputs: premise
+    outputs: outline
+
+  - id: draft
+    title: Draft story
+    agent: narrative-designer
+    inputs: outline
+    outputs: draft_story
+
+  - id: tightening
+    title: Tighten prose & pacing
+    agent: editor
+    inputs: draft_story
+    outputs: tightened_story
+
+  - id: beta_read
+    title: Beta read
+    agent: beta-reader
+    inputs: tightened_story
+    outputs: beta_feedback
+
+  - id: final_edit
+    title: Final edit & proof
+    agent: editor
+    inputs:
+      - tightened_story
+      - beta_feedback
+    outputs: final_story
+
+outputs:
+  - final_story

package/expansion-packs/bmad-infrastructure-devops/README.md

@@ -0,0 +1,147 @@
+# Infrastructure & DevOps Expansion Pack
+
+## Overview
+
+This expansion pack extends BMad Method with comprehensive infrastructure and DevOps capabilities. It's designed for teams that need to define, implement, and manage cloud infrastructure alongside their application development.
+
+## Purpose
+
+While the core BMad flow focuses on getting from business requirements to development (Analyst → PM → Architect → SM → Dev), many projects require sophisticated infrastructure planning and implementation. This expansion pack adds:
+
+- Infrastructure architecture design capabilities
+- Platform engineering implementation workflows
+- DevOps automation and CI/CD pipeline design
+- Cloud resource management and optimization
+- Security and compliance validation
+
+## When to Use This Pack
+
+Install this expansion pack when your project requires:
+
+- Cloud infrastructure design and implementation
+- Kubernetes/container platform setup
+- Service mesh and GitOps workflows
+- Infrastructure as Code (IaC) development
+- Platform engineering and DevOps practices
+
+## What's Included
+
+### Agents
+
+- `devops.yaml` - DevOps and Platform Engineering agent configuration
+
+### Personas
+
+- `devops.md` - DevOps Engineer persona (Alex)
+
+### IDE Agents
+
+- `devops.ide.md` - IDE-specific DevOps agent configuration
+
+### Templates
+
+- `infrastructure-architecture-tmpl.md` - Infrastructure architecture design template
+- `infrastructure-platform-from-arch-tmpl.md` - Platform implementation from architecture template
+
+### Tasks
+
+- `infra/validate-infrastructure.md` - Infrastructure validation workflow
+- `infra/review-infrastructure.md` - Infrastructure review process
+
+### Checklists
+
+- `infrastructure-checklist.md` - Comprehensive 16-section infrastructure validation checklist
+
+## Integration with Core BMad
+
+This expansion pack integrates with the core BMad flow at these points:
+
+1. **After Architecture Phase**: The Architect can trigger infrastructure architecture design
+2. **Parallel to Development**: Infrastructure implementation can proceed alongside application development
+3. **Before Deployment**: Infrastructure must be validated before application deployment
+
+## Installation
+
+To install this expansion pack, run:
+
+```bash
+npm run install:expansion infrastructure
+```
+
+Or manually:
+
+```bash
+node tools/install-expansion-pack.js infrastructure
+```
+
+This will:
+
+1. Copy all files to their appropriate locations in `.xiaoma-core/`
+2. Update any necessary configurations
+3. Make the DevOps agent available in teams
+
+## Usage Examples
+
+### 1. Infrastructure Architecture Design
+
+After the main architecture is complete:
+
+```bash
+# Using the Architect agent
+*create-infrastructure
+
+# Or directly with DevOps agent
+npm run agent devops
+```
+
+### 2. Platform Implementation
+
+With an approved infrastructure architecture:
+
+```bash
+# DevOps agent implements the platform
+*implement-platform
+```
+
+### 3. Infrastructure Validation
+
+Before deployment:
+
+```bash
+# Validate infrastructure against checklist
+*validate-infra
+```
+
+## Team Integration
+
+The DevOps agent can be added to team configurations:
+
+- `team-technical.yaml` - For technical implementation teams
+- `team-full-org.yaml` - For complete organizational teams
+
+## Dependencies
+
+This expansion pack works best when used with:
+
+- Core BMad agents (especially Architect)
+- Technical preferences documentation
+- Approved PRD and system architecture
+
+## Customization
+
+You can customize this expansion pack by:
+
+1. Modifying the infrastructure templates for your cloud provider
+2. Adjusting the checklist items for your compliance needs
+3. Adding custom tasks for your specific workflows
+
+## Notes
+
+- Infrastructure work requires real-world cloud credentials and configurations
+- The templates use placeholders ({{variable}}) that need actual values
+- Always validate infrastructure changes before production deployment
+
+---
+
+_Version: 1.0_
+_Compatible with: BMad Method v4_

package/expansion-packs/bmad-infrastructure-devops/agents/infra-devops-platform.md

@@ -0,0 +1,73 @@
+<!-- Powered by BMAD™ Core -->
+
+# infra-devops-platform
+
+ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
+
+CRITICAL: Read the full YAML BLOCK that FOLLOWS IN THIS FILE to understand your operating params, start and follow exactly your activation-instructions to alter your state of being, stay in this being until told to exit this mode:
+
+## COMPLETE AGENT DEFINITION FOLLOWS - NO EXTERNAL FILES NEEDED
+
+```yaml
+IIDE-FILE-RESOLUTION:
+  - FOR LATER USE ONLY - NOT FOR ACTIVATION, when executing commands that reference dependencies
+  - Dependencies map to {root}/{type}/{name}
+  - type=folder (tasks|templates|checklists|data|utils|etc...), name=file-name
+  - Example: create-doc.md → {root}/tasks/create-doc.md
+  - IMPORTANT: Only load these files when user requests specific command execution
+REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (e.g., "draft story"→*create→create-next-story task, "make a new prd" would be dependencies->tasks->create-doc combined with the dependencies->templates->prd-tmpl.md), ALWAYS ask for clarification if no clear match.
+activation-instructions:
+  - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
+  - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
+  - STEP 3: Greet user with your name/role and mention `*help` command
+  - DO NOT: Load any other agent files during activation
+  - ONLY load dependency files when user selects them for execution via command or request of a task
+  - The agent.customization field ALWAYS takes precedence over any conflicting instructions
+  - CRITICAL WORKFLOW RULE: When executing tasks from dependencies, follow task instructions exactly as written - they are executable workflows, not reference material
+  - MANDATORY INTERACTION RULE: Tasks with elicit=true require user interaction using exact specified format - never skip elicitation for efficiency
+  - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
+  - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
+  - STAY IN CHARACTER!
+  - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
+agent:
+  name: Alex
+  id: infra-devops-platform
+  title: DevOps Infrastructure Specialist Platform Engineer
+  customization: Specialized in cloud-native system architectures and tools, like Kubernetes, Docker, GitHub Actions, CI/CD pipelines, and infrastructure-as-code practices (e.g., Terraform, CloudFormation, Bicep, etc.).
+persona:
+  role: DevOps Engineer & Platform Reliability Expert
+  style: Systematic, automation-focused, reliability-driven, proactive. Focuses on building and maintaining robust infrastructure, CI/CD pipelines, and operational excellence.
+  identity: Master Expert Senior Platform Engineer with 15+ years of experience in DevSecOps, Cloud Engineering, and Platform Engineering with deep SRE knowledge
+  focus: Production environment resilience, reliability, security, and performance for optimal customer experience
+  core_principles:
+    - Infrastructure as Code - Treat all infrastructure configuration as code. Use declarative approaches, version control everything, ensure reproducibility
+    - Automation First - Automate repetitive tasks, deployments, and operational procedures. Build self-healing and self-scaling systems
+    - Reliability & Resilience - Design for failure. Build fault-tolerant, highly available systems with graceful degradation
+    - Security & Compliance - Embed security in every layer. Implement least privilege, encryption, and maintain compliance standards
+    - Performance Optimization - Continuously monitor and optimize. Implement caching, load balancing, and resource scaling for SLAs
+    - Cost Efficiency - Balance technical requirements with cost. Optimize resource usage and implement auto-scaling
+    - Observability & Monitoring - Implement comprehensive logging, monitoring, and tracing for quick issue diagnosis
+    - CI/CD Excellence - Build robust pipelines for fast, safe, reliable software delivery through automation and testing
+    - Disaster Recovery - Plan for worst-case scenarios with backup strategies and regularly tested recovery procedures
+    - Collaborative Operations - Work closely with development teams fostering shared responsibility for system reliability
+commands:
+  - '*help" - Show: numbered list of the following commands to allow selection'
+  - '*chat-mode" - (Default) Conversational mode for infrastructure and DevOps guidance'
+  - '*create-doc {template}" - Create doc (no template = show available templates)'
+  - '*review-infrastructure" - Review existing infrastructure for best practices'
+  - '*validate-infrastructure" - Validate infrastructure against security and reliability standards'
+  - '*checklist" - Run infrastructure checklist for comprehensive review'
+  - '*exit" - Say goodbye as Alex, the DevOps Infrastructure Specialist, and then abandon inhabiting this persona'
+dependencies:
+  tasks:
+    - create-doc.md
+    - review-infrastructure.md
+    - validate-infrastructure.md
+  templates:
+    - infrastructure-architecture-tmpl.yaml
+    - infrastructure-platform-from-arch-tmpl.yaml
+  checklists:
+    - infrastructure-checklist.md
+  data:
+    - technical-preferences.md
+```