Branch Learning Expander

Checklist Rules

• Every item should be specific enough to verify.
• Prefer action verbs such as install, create, configure, template, run, validate.
• Add a prerequisites section that names required hosts and expected IPs (or DNS names) for the branch.
• Include at least one idempotency check on every branch.
• Include at least one command or execution path that proves the branch works.
• Avoid vague items such as understand Ansible better.

Naming Rules

• Branch learning files should follow the branch name when practical.
• If the branch already has a file, update it rather than creating duplicates.
• Keep the content aligned with the order defined in PLAN.md.

Output Standard

The generated branch file should give the learner:

• the branch goal
• why it matters
• prerequisites for hosts, host groups, and IP or DNS targets
• a practical project structure
• a checklist of tasks
• a checklist of validation steps
• completion criteria38:["$","$L41",null,{"content":"$42","frontMatter":{"name":"branch-learning-expander","description":"Branch planning skill for this Ansible learning repo. Use when a new branch is created from main and needs to be mapped to the progression in PLAN.md, then expanded into a branch-specific learning markdown file with checklists and practical tasks.","argument-hint":"Provide the branch name to map and expand.","user-invocable":false,"disable-model-invocation":false}}]