Add Cursor skill to review assemblies for single user story

[aneta-petrova]

What changes are you introducing?

Add a new Cursor skill that reviews assembly files to ensure they follow the one-user-story principle. The skill analyzes assemblies and can split them into multiple files if they contain multiple independent user stories.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

The requirement that each assembly is a single user story is part of the downstream Content Quality Assessment checklist.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

N/A

Contributor checklists

• I am okay with my commits getting squashed when you merge this PR.
• I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• Foreman 3.18/Katello 4.20 (Satellite 6.19)
• Foreman 3.17/Katello 4.19
• Foreman 3.16/Katello 4.18 (Satellite 6.18; orcharhino 7.6 and 7.7)
• Foreman 3.15/Katello 4.17
• Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4; orcharhino 7.5)
• Foreman 3.13/Katello 4.15 (EL9 only)
• Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
• We do not accept PRs for Foreman older than 3.12.

[github-actions]

The PR preview for 4be0c6a is available at theforeman-foreman-documentation-preview-pr-4723.surge.sh

No diff compared to the current base

show diff