Clarify toolkit skill delegation during project bootstrap

[dieterbaier]

Projects that reference architecture-knowledge-toolkit should not have to copy individual workflow rules locally. Instead, their project instructions should delegate architecture and workflow tasks to the canonical toolkit contracts and skills.

Problem

A target project can state that it uses architecture-knowledge-toolkit, but agents may still miss toolkit workflow conventions when those conventions are not explicitly referenced in the target repository. A recent example was issue-based commit messages: the toolkit skills/commit-message/SKILL.md defines the issue_<number>: <summary> format, but the target project only had a broad toolkit reference, so the convention was not applied reliably.

Goal

Make bootstrap output and agent guidance explicit enough that target projects inherit relevant toolkit contracts and skills by reference, without duplicating all toolkit rules.

Suggested Changes

• Update skills/bootstrap-project/SKILL.md so project bootstrap explicitly installs or verifies target-project guidance that delegates to toolkit skills and contracts.
• Clarify that the toolkit is the canonical source not only for architecture documentation, templates, metamodels, validators, and generators, but also for task/workflow skills such as:
  • skills/implement-issue-workflow/SKILL.md
  • skills/commit-message/SKILL.md
  • skills/pr-review/SKILL.md
  • skills/slice-issues/SKILL.md
  • skills/adr/SKILL.md
  • skills/risk/SKILL.md
  • skills/quality-scenario/SKILL.md
  • skills/traceability-review/SKILL.md
• Update templates/agents/project-agents.md to mention issue implementation, commit messages, pull request review, and issue slicing explicitly.
• Optionally update templates/agents/global-agent-instructions.md so global discovery guidance mentions toolkit task/workflow skills in addition to architecture documentation conventions.
• Add a bootstrap checklist item: verify that the target project’s AGENTS.md or general-semantic-contracts.md delegates applicable tasks to toolkit skills instead of recreating rules locally.

Acceptance Criteria

• Bootstrapped target projects receive clear guidance to use toolkit skills for architecture and workflow tasks.
• Issue implementation in target projects points to implement-issue-workflow and commit-message.
• Pull request review in target projects points to pr-review.
• The guidance preserves project-local precedence: local project instructions may deliberately narrow or override toolkit rules.
• The guidance avoids copying all toolkit rules into target projects; it references the toolkit as the source of truth.

[dieterbaier]

Implemented the issue #36 guidance on branch codex/issue-36-toolkit-sdl-delegation.

Scope:

• clarified skills/bootstrap-project/SKILL.md so missing target-project SDLC task guidance must be delegated to the toolkit before acting;
• updated templates/agents/project-agents.md, templates/agents/global-agent-instructions.md, and templates/agents/github-copilot-instructions.md to mention issue slicing, issue implementation, commit messages, PR reviews, ADRs, quality scenarios, risks, and traceability reviews explicitly;
• added the same dependency rule to AGENTS.md and general-semantic-contracts.md so the toolkit contract itself carries the expectation.

Verification:

• ruby scripts/validate-metamodel.rb passes with 0 errors; existing bidirectional-relation warnings remain;
• ruby -Itest test/validate_metamodel_test.rb passes with 13 runs and 82 assertions.

[dieterbaier]

Follow-up: clarified the remote fallback as well.

When the architecture-knowledge-toolkit is not available on the local filesystem, the contracts/templates now explicitly direct agents to use the public repository as the fallback source of truth:

https://github.com/docs-as-code-toolkit/architecture-knowledge-toolkit

Updated in:

• AGENTS.md
• general-semantic-contracts.md
• templates/agents/project-agents.md
• templates/agents/global-agent-instructions.md
• templates/agents/github-copilot-instructions.md

Verification still passes:

• ruby scripts/validate-metamodel.rb: 0 errors, existing bidirectional-relation warnings remain
• ruby -Itest test/validate_metamodel_test.rb: 13 runs, 82 assertions, 0 failures