skills.rest
apolosan
apolosanCOMMUNITY
Explore all skills by this author →
GitHub

up-contracts

Generate System Operation Contracts from System Sequence Diagrams with OCL post-conditions.

3|Updated Mar 31, 2026
Search Tags:#design#contracts#preconditions#postconditions#ssd#system-operation#ocl
One-click install
npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-contracts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: up-contracts
Source: https://github.com/apolosan/unified_process_pi_extension/tree/main/skills/up-contracts
Command: npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalize observable behavior of software operations by converting system sequence diagrams into contracts that specify pre-conditions and five post-condition types (attribute modification, instance creation, association creation, instance destruction, association destruction) and exceptions.

Core Features & Use Cases

  • Generate per-operation System Operation Contracts from SSDs, including pre-conditions and all five post-condition types.
  • Generate a standard contract template and organize artifacts under docs/up/06-contracts/.

Quick Start

Execute a sample SSD and generate its complete operation contract.

Frequently Asked Questions about up-contracts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate system operation contracts from a system sequence diagram?▼

Generated system operation contracts are organized as artifact files under a dedicated directory structure like docs/up/06-contracts/, ensuring per-operation documentation remains accessible and properly structured.

What are the OCL post-condition types used in system operation contracts?▼

OCL post-conditions in system operation contracts define five behavior types: attribute modification, instance creation, association creation, instance destruction, and association destruction, which formalize observable software operation changes.

When do I need to create system operation contracts in object-oriented design?▼

System operation contracts are needed after creating an SSD to formalize the observable behavior of software operations by specifying strict pre-conditions, OCL post-conditions, and exceptions before implementation begins.

What input files do I need to create system operation contracts?▼

Generating system operation contracts requires an existing system sequence diagram and a conceptual model as inputs, typically structured as markdown files, to drive the template-driven contract creation workflow.

How are generated system operation contract artifacts organized?▼

Generated system operation contracts are organized as artifact files under a dedicated directory structure like docs/up/06-contracts/, ensuring per-operation documentation remains accessible and properly structured.

Related Skills

Explore More Software Engineering Skills→
apolosanapolosan
3

up-conceptual-model

Generate a Mermaid class diagram and documentation from UP use-case documents and SSDs.

Community
Advanced
rainoftimerainoftime
17

hoare-logic-verifier

Verify imperative program correctness using Hoare logic and loop invariants.

Community
Intermediate
zhongadamwangzhongadamwang

diagram-generatecollaboration

Generate Mermaid collaboration diagrams from domain concepts and requirements.

Community
Advanced
Obsidian-OwlObsidian-Owl
1

dev.tasks

Convert feature design artifacts into a dependency-ordered tasks.md file.

Official
Advanced