Files
sar/.agents/skills/bmad-quick-dev/sync-sprint-status.md
julian 17c08e6392 chore: initial monorepo scaffold + WDS Phase 1+2 artifacts
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-27 14:34:20 +00: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.