d3163a5bff
- pgSchema "mesh" with 4 tables isolating the peer mesh domain - Enums: visibility, transport, tier, role - audit_log is metadata-only (E2E encryption enforced at broker/client) - Cascade on mesh delete, soft-delete via archivedAt/revokedAt Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.1 KiB
description, auto_execution_mode
| description | auto_execution_mode |
|---|---|
| sprint-planning | 1 |
name: sprint-planning description: "Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle" author: "BMad"
Critical variables from config
config_source: "{project-root}/_bmad/bmm/config.yaml" output_folder: "{config_source}:output_folder" user_name: "{config_source}:user_name" communication_language: "{config_source}:communication_language" date: system-generated sprint_artifacts: "{config_source}:sprint_artifacts"
Workflow components
installed_path: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning" instructions: "{installed_path}/instructions.md" template: "{installed_path}/sprint-status-template.yaml" validation: "{installed_path}/checklist.md"
Variables and inputs
variables:
Project context
project_context: "**/project-context.md"
Project identification
project_name: "{config_source}:project_name"
Tracking system configuration
tracking_system: "file-system" # Options: file-system, Future will support other options from config of mcp such as jira, linear, trello story_location: "{config_source}:sprint_artifacts" # Relative path for file-system, Future will support URL for Jira/Linear/Trello story_location_absolute: "{config_source}:sprint_artifacts" # Absolute path for file operations
Source files (file-system only)
epics_location: "{output_folder}" # Directory containing epic*.md files epics_pattern: "epic*.md" # Pattern to find epic files
Output configuration
status_file: "{sprint_artifacts}/sprint-status.yaml"
Smart input file references - handles both whole docs and sharded docs
Priority: Whole document first, then sharded version
Strategy: FULL LOAD - sprint planning needs ALL epics to build complete status
input_file_patterns: epics: description: "All epics with user stories" whole: "{output_folder}/epic.md" sharded: "{output_folder}/epic/*.md" load_strategy: "FULL_LOAD"
Output configuration
default_output_file: "{status_file}"
standalone: true