Module development workflow from scaffold to integration. Keywords: module, workflow, development.
This workflow describes the canonical way to create or modify modules while preserving registries, strategy boundaries, and auditability.
Use this workflow when you need to:
/modules/<module_id>/MANIFEST.yaml, flows, or abilitiesOut of scope:
Inputs:
module_id (stable identifier)Preconditions:
/AGENTS.md/modules/AGENTS.md/modules/<module_id>/AGENTS.md (if the module exists)/modules/integration/ (scenario + workdocs)./modules/<module_id>/ (if new)./modules/<module_id>/AGENTS.md exists and defines safe boundaries.MANIFEST.yaml exists and has the required fields.Reference templates:
/.system/skills/ssot/repo/scaffolding/new-module/template/layout.md/.system/skills/ssot/repo/scaffolding/new-module/template/manifest_fields.mdExamples:
MANIFEST.yaml flows/abilities declarations.src/ (and tests as appropriate).Rules:
/modules/overview/)./.system/skills/ssot/** and ensure the skill entrypoint references them.Never edit tool-owned marker blocks inside ABILITY.md (or generated provider skill wrappers).
Typical outputs:
/modules/<module_id>/MANIFEST.yaml, code, tests)/modules/overview/AGENTS.md as strategy only; put reusable explanations in /.system/skills/ssot/** supporting docs./.system/skills/ssot/repo/architecture-core-mechanisms/modular-system/SKILL.md/.system/skills/ssot/repo/architecture-core-mechanisms/ability-workflow/SKILL.md/.system/skills/ssot/repo/scaffolding/new-module/template/registration_flow.md