Skip to content

P3: Concurrency primitive for parallel /dev sessions on the same sprint #40

@ramdhanyk

Description

@ramdhanyk

Source: 2026-04-20 multi-expert AADM audit. Methodology auditor.

Problem

Two engineers running /dev on the same sprint have no concurrency primitive. reconcile.py is read-only. sprint_close.py has no in-progress lock. Conflict surfaces only at merge time.

Fix

Minimum viable: sprints/vN/.dev-in-progress/T-12.{user}.lock file the /dev skill creates on start and removes on PR open. Skill warns (not blocks) if another user holds the lock for the same task.

Acceptance

Two simultaneous /dev invocations on task T-12 produce a visible warning naming the other holder.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Lower-stakes fillsaudit-followupFrom the 2026-04-20 multi-expert AADM audit

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions