WIP: docs: add Feature & Component Modelling How-To and Requirements Inspection agent

[antonkri]

WIP

For now, just for sharing with other colleagues, no merging planned yet

Summary

Adds a practical, step-by-step Feature & Component Modelling How-To plus the Requirements Inspection agent that automates the first inspection checklist.

Contents

docs/contribute/development/modelling_howto.rst (new, linked from docs/contribute/development/index.rst)

Step-by-step guide covering the reduced metamodel actually in use today:

• Which sphinx-needs directives to write on the feature side (score repo: stkh_req, feat_req, feat, logic_arc_int(_op)) vs. on the realisation side (module repos: feat_arc_sta/_dyn, mod/mod_view_sta, comp/comp_arc_sta, comp_req).
• The required cross-repo links (belongs_to / fulfils / satisfies / implements).
• Where each inspection checklist lives and how to set it up, with direct links to the official process_description folder templates (pinned to v1.5.4, the version score consumes via bazel_dep).
• Step 5 sub-section explains how to invoke the new Requirements Inspection agent.

.github/agents/req-inspection.agent.md + .github/skills/req-inspection-checklist/SKILL.md (new)

• Agent definition and companion skill.
• Scaffolds and fills chklst_req_inspection.rst for a single S-CORE feature per invocation.
• Scope: feature-level feat_req inspections in the score repo. Component-level comp_req inspections in module repos are not yet supported and the agent stops when given a module/component name.
• Invocation: copilot --allow-all-tools --agent "Requirements Inspection" -p "<feature-name>"

Build

bazel run //:docs_check passes (only the 6 pre-existing non-fatal warnings on lifecycle remain, unrelated to this change).

[github-actions]

The created documentation from the pull request is available at: docu-html

[github-actions]

Thanks for the pull request. This thread has been quiet for 30 days, so we are marking it as stale for now. Please take a quick look and let us know whether it is still up to date, still relevant, needs review, or is ready to merge. Any new activity will remove the stale label automatically. If nothing changes in the next 10 days, we will close it to keep the backlog current.