🏆 OKR: The framework handles complexity so authors don't have to

[MariusStorhaug]

Objective: The framework handles complexity so authors don't have to

The framework should absorb operational complexity — versioning, cross-platform testing, documentation generation, linting, publishing — so that module authors can focus entirely on the PowerShell code they care about.

Key Results

• KR1: Minimal configuration — The default PSModule.yml requires zero lines of config for the common case (build, test, publish a module)
• KR2: Manual steps eliminated — From PR open to published module, zero manual steps beyond writing code and applying a label
• KR3: Single workflow — One reusable workflow handles the entire lifecycle (no multi-workflow orchestration burden on consumers)
• KR4: Transparent decisions — Every version bump, skip, or publish decision is explained in PR comments or workflow summaries without the author needing to debug

What "handles complexity" means

• Authors don't need to understand SemVer mechanics — labels drive it.
• Authors don't need to configure CI matrices — defaults cover all platforms.
• Authors don't need to wire up documentation — the framework generates and publishes it.
• Authors don't need to manage prerelease versions — the framework handles incrementing, cleanup, and promotion.
• Build once, test the built artifact, publish the tested artifact — no drift.

Initiatives (linked as sub-issues)

Initiatives that move these KRs will be added as sub-issues below.