MCAF: Agile Delivery
Start from the user's delivery problem and existing team agreements. Follow AGENTS.md when editing repository guidance.
Workflow
- Find the concrete bottleneck in readiness, ownership, review, handoff, or feedback.
- Define a lightweight agreement with an owner, observable completion condition, and a way to assess whether it improved delivery.
- Keep backlog items coherent and reviewable with scope, acceptance, and constraints. Do not replace a requested complete feature with an unapproved subset.
- Record accepted recurring rules in the team's canonical docs; feature behavior belongs in specs and architecture decisions in ADRs.
- Check that the agreement fixes the stated problem without creating unrelated ceremonies, roles, or mandatory artifacts.
Deliver the requested team agreement or recommendation. Do not notify teammates or change external boards without authorization.
References
- For backlog and feedback conventions: agile delivery.
- When clarifying responsibilities: roles.