orgmodel-update

Update organizational model documents and folder structures from domain analysis outputs.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/zhongadamwang/CCAGA --skill orgmodel-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orgmodel-update
Source: https://github.com/zhongadamwang/CCAGA/tree/main/.github/skills/orgmodel-update
Command: npx skills add https://github.com/zhongadamwang/CCAGA --skill orgmodel-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizational modeling often becomes outdated as requirements evolve, making it hard to keep process, domain, and collaboration documentation aligned.

Core Features & Use Cases

  • Automates updates to the orgModel hierarchy based on domain analysis results and collaboration diagrams.
  • Generates and updates main.md, domain-model.md, process.md, collaboration.md, vocabulary.md, and test-case-list.md while preserving existing content and references.
  • Supports traceability by referencing source requirements and maintaining cross-reference integrity.

Quick Start

Generate or update the orgModel/[NN] - [Process Name]/ with the latest domain concepts, alignment results, and collaboration diagrams.

Frequently Asked Questions about orgmodel-update

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

FAQPage Schema
How do I keep organizational model documents synced with new requirements?

Updating domain model documents involves generating and validating files like domain-model.md and process.md. The system processes domain analysis outputs to refresh the orgModel hierarchy while preserving existing references and maintaining traceability.

Can I update process and collaboration documentation without losing existing references?

Yes, updating process and collaboration documentation preserves existing content and cross-reference integrity. The system refreshes main.md, collaboration.md, and vocabulary.md while maintaining traceability to source requirements.

What is the best way to maintain traceability across organizational models?

The best way to maintain traceability is by referencing source requirements when refreshing the orgModel hierarchy. This ensures cross-reference integrity across main.md, domain-model.md, and test-case-list.md while preserving existing content.

Does this organizational model update approach work without external dependencies?

Yes, this organizational model update approach operates without external dependencies. It processes domain analysis outputs and collaboration diagrams internally to generate and validate the required markdown files.

When do I need to refresh the orgModel folder structure?

You need to refresh the orgModel folder structure when organizational modeling becomes outdated as requirements evolve. This ensures process, domain, and collaboration documentation stays aligned by generating updated markdown files.