docs: repair MSX documentation links

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Author: MariusStorhaug

.github/plugin/psmodule/skills/psmodule-module-development-orchestration/SKILL.md

@@ -71,7 +71,7 @@ changes, or claim release readiness.
 - [Module development orchestration](../../../../../docs/content/guides/module-development-orchestration.md)
 - [PSModule repository standard](../../../../../docs/content/reference/repository-standard.md)
 - [Structuring your module](../../../../../docs/content/guides/structuring-your-module.md)
-- [MSX Agentic Development](https://msx.no/docs/Ways-of-Working/Agentic-Development/)
+- [MSX Agentic Development](https://msx.no/docs/Capabilities/agentic-development/)
 - [MSX Workflow](https://msx.no/docs/Ways-of-Working/Workflow/)
 - [MSX Branching and Merging](https://msx.no/docs/Ways-of-Working/Branching-and-Merging/)
 - [MSX PR format](https://msx.no/docs/Ways-of-Working/PR-Format/)

AGENTS.md

@@ -28,7 +28,7 @@ works. For PSModule-specific build, layout, and process guidance:
 
 For cross-cutting ways of working and standards:
 
-- [Agentic Development](https://msx.no/docs/Ways-of-Working/Agentic-Development/) —
+- [Agentic Development](https://msx.no/docs/Capabilities/agentic-development/) —
   how agents and humans collaborate in this ecosystem.
 - [Ways of Working](https://msx.no/docs/Ways-of-Working/) — contribution
   workflow, branching, PRs, issues.

docs/content/guides/validating-before-review.md

@@ -5,7 +5,7 @@ description: PSModule-specific validation checks that extend the shared MSXOrg B
 
 # Validating before review
 
-Use this page after scaffolding a module change or implementing a function and before you finish self-review or mark a draft pull request ready. It extends the shared MSXOrg [Workflow Build step](https://msx.no/docs/Ways-of-Working/Workflow/#build) and [Implement guidance](https://msx.no/docs/Agents/implement/) with the PSModule-specific validation checks that module repositories must pass.
+Use this page after scaffolding a module change or implementing a function and before you finish self-review or mark a draft pull request ready. It extends the shared MSXOrg [Workflow Build step](https://msx.no/docs/Ways-of-Working/Workflow/#build) and [Implement guidance](https://msx.no/docs/Ways-of-Working/Workflow-Stages/Implement/) with the PSModule-specific validation checks that module repositories must pass.
 
 Do not repeat the shared workflow here. Follow the shared branch → draft PR → implement → test → self-review loop first, then run this PSModule pass to confirm the change still fits the module's design, documentation, and PowerShell standards.
 
@@ -79,15 +79,15 @@ Do not repeat the shared workflow here. Follow the shared branch → draft PR 
    Check:
 
    - naming, documentation, error handling, testing expectations, and security posture align with the relevant pages under [MSX Coding Standards](https://msx.no/docs/Coding-Standards/)
-   - the change follows the shared "written once, referenced everywhere" rule by linking canonical guidance instead of copying it into local docs or code comments, as described in [Agentic Development](https://msx.no/docs/Ways-of-Working/Agentic-Development/)
+   - the change follows the shared "written once, referenced everywhere" rule by linking canonical guidance instead of copying it into local docs or code comments, as described in [Agentic Development](https://msx.no/docs/Capabilities/agentic-development/)
    - the draft PR description, issue progress, and any follow-up issues reflect what actually shipped and what still belongs out of scope
 
    This is the last author-side gate before a PSModule draft PR is ready for independent review.
 
 ## Where this connects
 
 - [MSX Workflow Build step](https://msx.no/docs/Ways-of-Working/Workflow/#build)
-- [MSX Implement guidance](https://msx.no/docs/Agents/implement/)
+- [MSX Implement guidance](https://msx.no/docs/Ways-of-Working/Workflow-Stages/Implement/)
 - [PowerShell module standard](../reference/powershell-module-standard.md)
 - [Module types](../reference/module-types.md)
 - [Structuring your module](structuring-your-module.md)

docs/content/guides/writing-plugin-skills.md

@@ -88,7 +88,7 @@ update the skill without duplicating the common documentation.
 ## References
 
 - [PSModule process plugin](https://github.com/PSModule/Process-PSModule/tree/main/.github/plugin)
-- [MSX Agentic Development](https://msx.no/docs/Ways-of-Working/Agentic-Development/)
+- [MSX Agentic Development](https://msx.no/docs/Capabilities/agentic-development/)
 - [MSX Documentation Model](https://msx.no/docs/Ways-of-Working/Documentation-Model/)
 - [MSX Markdown standard](https://msx.no/docs/Coding-Standards/Markdown/)
 - [MSX Natural Language standard](https://msx.no/docs/Coding-Standards/Natural-Language/)

docs/content/index.md

@@ -89,4 +89,4 @@ Cross-org standards and reusable solution documentation are now canonical in [MS
 
 - [Coding Standards](https://msx.no/docs/Coding-Standards/)
 - [Capabilities](https://msx.no/docs/Capabilities/)
-- [Frameworks](https://msx.no/docs/Frameworks/)
+- [Frameworks](https://msx.no/docs/Capabilities/)

docs/content/reference/repository-standard.md

@@ -175,7 +175,7 @@ See [PSModule/Template-PSModule](https://github.com/PSModule/Template-PSModule)
 
 `AGENTS.md` and `CLAUDE.md` are the required set. `AGENTS.md` is the entry point that AGENTS.md-aware runtimes read directly, so a repository is usable by an agent without a per-runtime copy of the same pointer.
 
-Runtime-specific adapter files such as `.github/copilot-instructions.md` and `.github/instructions/*.instructions.md` are optional. MSX treats them as client adapters that *may* add runtime-specific loading or path rules, described in [Agentic Development](https://msx.no/docs/Ways-of-Working/Agentic-Development/) and its [capability specification](https://msx.no/docs/Capabilities/agentic-development/spec/). Add one when a runtime needs loading or path rules that `AGENTS.md` cannot express, and keep it pointing at `AGENTS.md` rather than restating it. `Template-PSModule` ships without one.
+Runtime-specific adapter files such as `.github/copilot-instructions.md` and `.github/instructions/*.instructions.md` are optional. MSX treats them as client adapters that *may* add runtime-specific loading or path rules, described in [Agentic Development](https://msx.no/docs/Capabilities/agentic-development/) and its [capability specification](https://msx.no/docs/Capabilities/agentic-development/spec/). Add one when a runtime needs loading or path rules that `AGENTS.md` cannot express, and keep it pointing at `AGENTS.md` rather than restating it. `Template-PSModule` ships without one.
 
 These files are the agent equivalent of the README: pointers, not copies. Keep them short so the linked documentation stays the single source of truth. Like the other governance files, they live in the repository itself so it can stand on its own.