Files
scrying-pool/.agents/skills/bmad-quick-dev/sync-sprint-status.md
T
uberwald 20d13fc678 Story 4.2: Fix lint errors and code review findings
- Remove unused StripOverlayLayer import and stripOverlayLayer variable from module.js
- Add comprehensive JSDoc annotations to FoundryAdapter.js methods (settings, socket, users, scenes, notifications, hooks)
- Add /* global Dialog */ comment to PlayerPrivacyPanel.js for ESLint
- Remove unused _force parameter from GMPlayerPrivacySelector.js render() method
- Fix PlayerPrivacyPanelMenu.js: add constructor() to fallback class and call super()

All 862 unit tests passing. All Story 4.2 acceptance criteria met.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
2026-05-24 01:25:30 +02:00

1.4 KiB

Sync Sprint Status

Shared sub-step for updating sprint-status.yaml during quick-dev. Called from any route (plan-code-review, one-shot, future routes) with a {target_status} parameter.

Preconditions

Skip this entire file (return to caller) if ANY of:

  • {story_key} is unset
  • {sprint_status} does not exist on disk

Instructions

  1. Load the FULL {sprint_status} file.
  2. Find the development_status entry matching {story_key}. If not found, warn the user once ("{story_key} not found in sprint-status; skipping sprint sync") and return to caller.
  3. Idempotency check. If development_status[{story_key}] is already at {target_status} or a later state (review is later than in-progress; done is later than both), return to caller — no write needed. Never regress a story's status.
  4. Set development_status[{story_key}] to {target_status}.
  5. Epic lift (only when {target_status} = in-progress). Derive the parent epic key as epic-{N} from the leading numeric segment of {story_key} (e.g., 3-2-digest-deliveryepic-3). If that entry exists and is backlog, set it to in-progress. Leave it alone otherwise. Skip this sub-step entirely when {target_status} is not in-progress.
  6. Refresh last_updated to the current date.
  7. Save the file, preserving ALL comments and structure including STATUS DEFINITIONS and WORKFLOW NOTES.