BMAD-METHOD

Commit Graph

Author	SHA1	Message	Date
Chandan Veerabhadrappa	09ce8559f2	fix: use last_updated instead of generated for sprint-status staleness check (#1836 ) The staleness warning in sprint-status always fired after 7 days because it checked the 'generated' timestamp, which is only set once during sprint-planning. Other workflows (dev-story, create-story, code-review, retrospective) update statuses but never touched 'generated'. This adds a 'last_updated' field that is: - Set initially alongside 'generated' during sprint-planning - Bumped to current date by every workflow that modifies sprint-status.yaml - Used by the staleness check (with fallback to 'generated' for backward compatibility) Fixes bmad-code-org/BMAD-METHOD#1820 Co-authored-by: Oz <oz-agent@warp.dev>	2026-03-06 20:25:59 -06:00
Brian Madison	6f8f0871cf	Project Cleanup of Agents Menus, BMB module removal to other repo	2026-01-19 02:04:14 -06:00

Author

SHA1

Message

Date

Chandan Veerabhadrappa

09ce8559f2

fix: use last_updated instead of generated for sprint-status staleness check (#1836 )

The staleness warning in sprint-status always fired after 7 days because
it checked the 'generated' timestamp, which is only set once during
sprint-planning. Other workflows (dev-story, create-story, code-review,
retrospective) update statuses but never touched 'generated'.

This adds a 'last_updated' field that is:
- Set initially alongside 'generated' during sprint-planning
- Bumped to current date by every workflow that modifies sprint-status.yaml
- Used by the staleness check (with fallback to 'generated' for backward
  compatibility)

Fixes bmad-code-org/BMAD-METHOD#1820

Co-authored-by: Oz <oz-agent@warp.dev>

2026-03-06 20:25:59 -06:00

Brian Madison

6f8f0871cf

Project Cleanup of Agents Menus, BMB module removal to other repo

2026-01-19 02:04:14 -06:00

2 Commits