Agentic-Development moves from the standalone Frameworks section into Capabilities, so it lives beside every other capability under the single spec-and-design model.
Context and request
Per #102, capability is the single concept and framework is only an adjective; the Frameworks section is being absorbed into Capabilities. Agentic-Development already carries spec.md, design.md, index.md, and memory-template.md, so this is a move, not new authoring.
The outcome: src/docs/Frameworks/Agentic-Development/ becomes src/docs/Capabilities/agentic-development/ (matching the lowercase-kebab folder style of the other capabilities such as release-management), registered in the nav under Capabilities, with every internal and inbound link updated. Front matter is preserved. Parent: #102.
Acceptance criteria: the four pages live under Capabilities/agentic-development/; the Capabilities nav lists Agentic Development in src/zensical.toml; no page still points at the old Frameworks/Agentic-Development/... path; the Frameworks index no longer lists it; and Update-DocumentationIndex.ps1 -Check and Test-DocumentationLink.ps1 both pass.
Technical decisions
Use git mv to preserve history. Folder name agentic-development (lowercase kebab) to match release-management, dependency-updates, etc. Update relative links inside the moved pages (e.g. ../../Ways-of-Working/... depth is unchanged since both are two levels deep, but verify) and any inbound links elsewhere in the docs that reference the old path (search Frameworks/Agentic-Development). Register in src/zensical.toml under Capabilities, removing the Frameworks entry for it. Do not remove the Frameworks section itself — that is the final child once Process-PSModule has also moved.
Implementation plan
Agentic-Development moves from the standalone Frameworks section into Capabilities, so it lives beside every other capability under the single spec-and-design model.
Context and request
Per #102,
capabilityis the single concept andframeworkis only an adjective; the Frameworks section is being absorbed into Capabilities. Agentic-Development already carriesspec.md,design.md,index.md, andmemory-template.md, so this is a move, not new authoring.The outcome:
src/docs/Frameworks/Agentic-Development/becomessrc/docs/Capabilities/agentic-development/(matching the lowercase-kebab folder style of the other capabilities such asrelease-management), registered in the nav under Capabilities, with every internal and inbound link updated. Front matter is preserved. Parent: #102.Acceptance criteria: the four pages live under
Capabilities/agentic-development/; the Capabilities nav lists Agentic Development insrc/zensical.toml; no page still points at the oldFrameworks/Agentic-Development/...path; the Frameworks index no longer lists it; andUpdate-DocumentationIndex.ps1 -CheckandTest-DocumentationLink.ps1both pass.Technical decisions
Use
git mvto preserve history. Folder nameagentic-development(lowercase kebab) to matchrelease-management,dependency-updates, etc. Update relative links inside the moved pages (e.g.../../Ways-of-Working/...depth is unchanged since both are two levels deep, but verify) and any inbound links elsewhere in the docs that reference the old path (searchFrameworks/Agentic-Development). Register insrc/zensical.tomlunder Capabilities, removing the Frameworks entry for it. Do not remove the Frameworks section itself — that is the final child once Process-PSModule has also moved.Implementation plan
git mv src/docs/Frameworks/Agentic-Development src/docs/Capabilities/agentic-development.src/zensical.toml: add the Agentic Development group under Capabilities, remove it from Frameworks.Frameworks/Agentic-DevelopmentandFrameworks/index.mdcross-links).Update-DocumentationIndex.ps1andTest-DocumentationLink.ps1; fix anything flagged; run markdownlint with.github/linters/.markdown-lint.yml.