03-descriptive-modeling

name	03-descriptive-modeling
description	Use when modelling requirement behaviour with scenarios, flows, states, activities, and domain views after the system context is known; use logic-modeling for formal decision logic.
metadata	{"portable":true,"compatible_with":["claude-code","codex"]}

[MISSING FILE FALLBACK] This skill references auxiliary files (logic.prompt, Python scripts) for automated execution. If those files are unavailable in your environment, Claude can execute this skill directly:

1. Read all files in projects/<ProjectName>/_context/
2. Follow the step-by-step instructions in the Manual Execution section below (or ask Claude to generate the relevant SRS section by describing the context inline)
3. Write output to projects/<ProjectName>/02-requirements-engineering/01-srs/<section-file>.md

This skill is fully executable without Python or logic.prompt by providing context directly to Claude.

Descriptive Modeling Skill Guidance

Use When

• modelling requirement behaviour with scenarios, flows, states, activities, and domain views after the system context is known; use logic-modeling for formal decision logic.
• Use this procedure when the required source artefacts are available and Descriptive behaviour models is the next lifecycle deliverable.

Do Not Use When

• Use logic-modeling when that neighbouring route owns the decision or deliverable.
• Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.