MCAF: Agile Delivery

Trigger On

• the team needs backlog, ceremony, role, or feedback-loop rules
• delivery process is vague, too heavy, or living only in chat
• recurring team pain needs to become durable repo guidance

Workflow

1. Keep delivery artefacts concrete:

- backlog - roles - ceremonies - engineering feedback

1. Prefer lightweight agreements over process theatre.
2. When a pain point repeats, turn it into a rule, doc, or skill update.
3. Pull only the references that match the current process problem.

Deliver

• concrete delivery guidance
• durable team agreements
• feedback loops that update docs, skills, and rules

Validate

• the process guidance fixes a real delivery problem
• roles and rituals are explicit enough to use
• recurring pain is converted into a durable artifact, not more chat

Load References

Related skills