agentleFS
Postpartum-genushyacinthus29Postpartum-genushyacinthus29/dotnet-skills/skills/dotnet-mcaf-agile-delivery/SKILL.md

dotnet-mcaf-agile-delivery

Skill13 starsChanged 8 months agoMITView on GitHub

Apply MCAF agile-delivery guidance for backlog quality, roles, ceremonies, and engineering feedback. Use when defining how the team plans, tracks work, and turns feedback into durable improvements.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    leave reusable project context so future tasks are faster and safer

    line 21
  2. Distinctive:

    Read the nearest AGENTS.md and confirm scope and constraints.

    line 36
  3. Very specific:

    Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.

    line 37
  4. Distinctive:

    Keep delivery artefacts concrete:

    line 42
  5. Distinctive:

    Prefer lightweight agreements over process theatre.

    line 47
  6. Distinctive:

    When a pain point repeats, turn it into a rule, doc, or skill update.

    line 48
  7. Distinctive:

    Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

    line 65
  8. Distinctive:

    write a detailed execution plan from the chosen direction

    line 73
  9. Distinctive:

    Update the plan after each iteration.

    line 78
  10. Very specific:

    If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • repo governance that belongs in AGENTS.md
  • feature planning for one specific feature doc

Inputs

  • the current delivery pain point
  • backlog, role, ceremony, and feedback mechanisms that already exist
  • where the team stores durable agreements, if anywhere

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Keep delivery artefacts concrete:
    • backlog
    • roles
    • ceremonies
    • engineering feedback
  2. Prefer lightweight agreements over process theatre.
  3. When a pain point repeats, turn it into a rule, doc, or skill update.
  4. 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

Ralph Loop

Use the Ralph Loop for every task, including docs, architecture, testing, and tooling work.

  1. Brainstorm first (mandatory):
    • analyze current state
    • define the problem, target outcome, constraints, and risks
    • generate options and think through trade-offs before committing
    • capture the recommended direction and open questions
  2. Plan second (mandatory):
    • write a detailed execution plan from the chosen direction
    • list final validation skills to run at the end, with order and reason
  3. Execute one planned step and produce a concrete delta.
  4. Review the result and capture findings with actionable next fixes.
  5. Apply fixes in small batches and rerun the relevant checks or review steps.
  6. Update the plan after each iteration.
  7. Repeat until outcomes are acceptable or only explicit exceptions remain.
  8. If a dependency is missing, bootstrap it or return status: not_applicable with explicit reason and fallback path.

Required Result Format

  • status: complete | clean | improved | configured | not_applicable | blocked
  • plan: concise plan and current iteration step
  • actions_taken: concrete changes made
  • validation_skills: final skills run, or skipped with reasons
  • verification: commands, checks, or review evidence summary
  • remaining: top unresolved items or none

For setup-only requests with no execution, return status: configured and exact next commands.

Load References

  • read references/agile-delivery.md first
  • open references/roles.md only for a narrower topic

Example Requests

  • "Define a lighter delivery model for this team."
  • "Turn repeated feedback pain into repo guidance."
  • "Fix our backlog and ceremony chaos."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.