Skip to main content
domain-proposenewconcepts Identify gaps in domain coverage and propose new concepts to address missing functionality or relationships. Analyzes domain alignment results to suggest conceptual extensions, validates proposals against requirements, and generates impact assessments for domain model evolution.
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/zhongadamwang/AI_Slowcooker --skill domain-proposenewconcepts명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... name domain-proposenewconcepts description Identify gaps in domain coverage and propose new concepts to address missing functionality or relationships. Analyzes domain alignment results to suggest conceptual extensions, validates proposals against requirements, and generates impact assessments for domain model evolution. license MIT
Domain Propose New Concepts
Analyze domain gaps and propose new concepts to enhance model completeness and address emerging requirements not covered by existing organizational domain models.
Intent
Systematically identify missing concepts in domain models by analyzing alignment gaps, requirement coverage, and emerging patterns. Proposes new domain concepts with clear justification, suggests integration approaches, and assesses impact on existing domain structures.
Inputs
Primary : projects/[project-name]/artifacts/Analysis/domain-alignment.json (from domain-alignentities skill)Secondary : projects/[project-name]/artifacts/Analysis/domain-concepts.json (from domain-extractconcepts skill)References : projects/[project-name]/artifacts/Analysis/requirements.json (for gap validation)References : Organizational domain models (orgModel/**/*domain-model.md)
Outputs
Files Generated:
projects/[project-name]/artifacts/Analysis/domain-newconcepts.json - Structured proposal data for programmatic useprojects/[project-name]/artifacts/Analysis/domain-newconcepts.md - Human-readable proposal report and planning
JSON Structure (domain-newconcepts.json)
{
"project_id" : "string" ,
"proposal_metadata" : {
"generated_at" : "ISO8601" ,
"source_alignment_file" : "domain-alignment.json" ,
"source_concepts_file" : "domain-concepts.json" ,
"reference_requirements" : "requirements.json" ,
"total_proposals" : "number" ,
"coverage_improvement" : "percentage" ,
"risk_assessment" : "low|medium|high"
} ,
"gap_analysis" : {
"coverage_gaps" : [
{
"gap_id" : "GAP-001" ,
"gap_type" : "missing_entity|missing_relationship|missing_process|missing_attribute" ,
"description" : Markdown Structure (domain-newconcepts.md)
# Domain New Concepts Proposal
**Project** : [project_id]
**Generated** : [timestamp]
**Analysis Source** : domain-alignment.json ([total_ alignments] alignments)
**Coverage Improvement** : [percentage]%
**Risk Level** : [risk_assessment]
## Executive Summary
**Gap Analysis Results** :
- **Coverage Gaps** : [count] | **Pattern Gaps** : [count] | **Relationship Gaps** : [count]
- **New Concept Proposals** : [count] | **Pattern Proposals** : [count] | **Relationship Proposals** : [count]
- **Requirements Coverage** : [before]% → [after]% improvement
**Implementation Impact** : [impact_ summary]
## Gap Analysis
### 🔍 Coverage Gaps Identified
#### GAP-001: Missing Progress Tracking *(High Priority)*
**Issue** : No concept for tracking skill progression over time
**Business Impact** : Cannot track learning progress effectively
**Evidence** :
- Multiple requirements reference progress tracking (R-005, R-012)
- No existing entity covers temporal skill development
**Affected Requirements** : R-005, R-012
### 🔄 Pattern Gaps Identified
#### PAT-001: Skills Development Lifecycle *(Medium Priority)*
**Missing Pattern** : No clear pattern for skill acquisition and mastery phases
**Domain Areas** : Learning, Assessment
**Requirements Needing Pattern** : R-003, R-008, R-015
### 🔗 Relationship Gaps Identified
#### RELA-001: Skill-Learning Resource Connection *(Medium Priority)*
**Missing Link** : Skill ↔ LearningResource relationship
Core Gap Analysis Process
1. Coverage Gap Detection
Requirement Mapping Analysis :
Unaddressed requirements : Requirements with no supporting domain conceptsPartially covered requirements : Requirements with incomplete concept supportOrphaned concepts : Domain concepts not linked to any requirementsFunctional holes : Missing concepts for complete business workflows
Entity Completeness Analysis :
Attribute gaps : Missing attributes needed for requirement fulfillmentRelationship gaps : Missing connections between related entitiesLifecycle gaps : Missing stages in entity lifecyclesData integrity gaps : Missing constraints and validation concepts
2. Pattern Gap Identification
Workflow Pattern Analysis :
Process incompleteness : Workflows missing start, middle, or end stagesDecision point gaps : Missing concepts for workflow branchingException handling gaps : Missing error and exception management conceptsIntegration pattern gaps : Missing concepts for system interactions
Structural Pattern Analysis :
Hierarchy gaps : Missing parent-child relationship patternsComposition gaps : Missing whole-part relationship patternsClassification gaps : Missing categorization and typing conceptsTemporal pattern gaps : Missing time-based relationship patterns
3. Concept Proposal Generation
Business Value Assessment :
Requirement coverage improvement : How much gap coverage increasesStakeholder value proposition : Clear benefits to business stakeholdersReusability potential : Can concept be useful across multiple projectsStrategic alignment : Fits with organizational domain model evolution
Technical Feasibility Analysis :
Implementation complexity : Development effort and technical challengesIntegration impact : Effect on existing systems and processesData requirements : New data needs and migration considerationsPerformance implications : System performance and scalability effects
4. Impact Assessment & Risk Analysis
Organizational Impact :
Model evolution : Changes to organizational domain modelsProcess changes : Updates to business processes and workflowsTraining needs : New concepts requiring stakeholder educationTool updates : Systems requiring modification or extension
Implementation Risk Assessment :
Technical risks : Development challenges and system integration issuesBusiness risks : Adoption challenges and process disruptionResource risks : Time, effort, and skill requirementsMitigation strategies : Approaches to minimize identified risks
Quality Assurance
Proposal Validation
Requirement traceability : All proposals linked to specific requirement gapsBusiness justification : Clear value proposition for each conceptImplementation feasibility : Realistic assessment of development effortOrganizational alignment : Consistency with existing domain models and standards
Gap Analysis Completeness
Systematic coverage : All domain areas analyzed for gapsMultiple perspective analysis : Entities, relationships, patterns, and processesStakeholder validation : Proposed concepts reviewed by domain expertsPriority ranking : Proposals prioritized by business value and implementation effort
For detailed gap analysis methodologies and concept proposal templates, see gap-analysis-patterns.md .
"No concept for tracking skill progression over time"
,
"affected_requirements"
:
[
"R-005"
,
"R-012"
]
,
"severity"
:
"high|medium|low"
,
"business_impact"
:
"Cannot track learning progress effectively"
,
"evidence"
:
[
"Multiple requirements reference progress tracking"
,
"No existing entity covers temporal skill development"
]
}
]
,
"pattern_gaps"
:
[
{
"pattern_id"
:
"PAT-001"
,
"pattern_type"
:
"workflow|lifecycle|hierarchy|communication"
,
"missing_pattern"
:
"Skills Development Lifecycle"
,
"description"
:
"No clear pattern for skill acquisition and mastery phases"
,
"domain_areas"
:
[
"Learning"
,
"Assessment"
]
,
"requirements_needing_pattern"
:
[
"R-003"
,
"R-008"
,
"R-015"
]
}
]
,
"relationship_gaps"
:
[
{
"gap_id"
:
"RELA-001"
,
"source_entity"
:
"Skill"
,
"target_entity"
:
"Learning Resource"
,
"missing_relationship_type"
:
"supported_by"
,
"justification"
:
"Skills need connection to learning materials"
,
"requirements_evidence"
:
[
"R-007"
,
"R-010"
]
}
]
}
,
"concept_proposals"
:
[
{
"proposal_id"
:
"PROP-001"
,
"concept_type"
:
"entity|process|attribute|relationship"
,
"name"
:
"SkillProgression"
,
"description"
:
"Tracks individual progress through skill development stages"
,
"fills_gap"
:
"GAP-001"
,
"domain_area"
:
"Learning Management"
,
"attributes"
:
[
{
"name"
:
"progression_id"
,
"type"
:
"identifier"
,
"description"
:
"Unique progression tracking identifier"
}
,
{
"name"
:
"current_level"
,
"type"
:
"enumeration"
,
"description"
:
"Current skill mastery level"
,
"values"
:
[
"novice"
,
"developing"
,
"proficient"
,
"expert"
]
}
,
{
"name"
:
"start_date"
,
"type"
:
"date"
,
"description"
:
"When skill development began"
}
,
{
"name"
:
"milestones"
,
"type"
:
"collection"
,
"description"
:
"Progress milestones achieved"
}
]
,
"relationships"
:
[
{
"target_entity"
:
"TeamMember"
,
"relationship_type"
:
"belongs_to"
,
"cardinality"
:
"many-to-one"
,
"description"
:
"Each progression belongs to one team member"
}
,
{
"target_entity"
:
"Skill"
,
"relationship_type"
:
"tracks"
,
"cardinality"
:
"many-to-one"
,
"description"
:
"Each progression tracks one specific skill"
}
]
,
"business_value"
:
{
"value_proposition"
:
"Enables systematic tracking of learning progress"
,
"benefits"
:
[
"Clear visibility into individual development"
,
"Data-driven skill planning"
,
"Progress reporting capabilities"
]
,
"metrics"
:
[
"Skill progression completion rates"
,
"Time to proficiency tracking"
,
"Learning effectiveness measurement"
]
}
,
"requirements_addressed"
:
[
{
"requirement_id"
:
"R-005"
,
"description"
:
"Track individual skill development"
,
"coverage_improvement"
:
"Provides complete progression tracking"
}
,
{
"requirement_id"
:
"R-012"
,
"description"
:
"Generate progress reports"
,
"coverage_improvement"
:
"Enables milestone-based reporting"
}
]
,
"implementation_considerations"
:
{
"integration_approach"
:
"extend|modify|standalone"
,
"organizational_alignment"
:
"Aligns with existing Team Member entity"
,
"data_requirements"
:
[
"Historical skill assessments"
,
"Learning milestone definitions"
,
"Progress tracking workflows"
]
,
"potential_conflicts"
:
[
{
"conflict"
:
"Overlaps with existing Assessment entity"
,
"resolution"
:
"SkillProgression aggregates multiple Assessments over time"
}
]
}
,
"risk_assessment"
:
{
"implementation_risk"
:
"low|medium|high"
,
"complexity"
:
"low|medium|high"
,
"organizational_impact"
:
"low|medium|high"
,
"mitigation_strategies"
:
[
"Pilot with single team first"
,
"Gradual rollout across organization"
,
"Clear documentation of differences from Assessment"
]
}
}
]
,
"pattern_proposals"
:
[
{
"pattern_id"
:
"PATP-001"
,
"pattern_name"
:
"Skills Development Lifecycle"
,
"pattern_type"
:
"workflow"
,
"fills_gap"
:
"PAT-001"
,
"description"
:
"Standard workflow for skill acquisition and mastery"
,
"phases"
:
[
{
"phase"
:
"Discovery"
,
"description"
:
"Identify skill needs and learning opportunities"
,
"entities_involved"
:
[
"TeamMember"
,
"Skill"
,
"LearningResource"
]
,
"key_activities"
:
[
"Skill gap assessment"
,
"Learning path planning"
]
}
,
{
"phase"
:
"Development"
,
"description"
:
"Active learning and skill building"
,
"entities_involved"
:
[
"SkillProgression"
,
"Assessment"
,
"LearningResource"
]
,
"key_activities"
:
[
"Learning activity completion"
,
"Progress tracking"
]
}
,
{
"phase"
:
"Validation"
,
"description"
:
"Demonstrate and validate skill mastery"
,
"entities_involved"
:
[
"Assessment"
,
"Skill"
,
"TeamMember"
]
,
"key_activities"
:
[
"Skill demonstration"
,
"Competency validation"
]
}
,
{
"phase"
:
"Application"
,
"description"
:
"Apply skills in real work contexts"
,
"entities_involved"
:
[
"TeamMember"
,
"Skill"
,
"WorkActivity"
]
,
"key_activities"
:
[
"Skill application"
,
"Performance monitoring"
]
}
]
,
"business_value"
:
"Provides standardized approach to skill development"
,
"implementation_impact"
:
"Requires workflow definition and training"
,
"requirements_supported"
:
[
"R-003"
,
"R-008"
,
"R-015"
]
}
]
,
"relationship_proposals"
:
[
{
"relationship_id"
:
"RELP-001"
,
"fills_gap"
:
"RELA-001"
,
"source_entity"
:
"Skill"
,
"target_entity"
:
"LearningResource"
,
"relationship_type"
:
"supported_by"
,
"cardinality"
:
"many-to-many"
,
"description"
:
"Skills are supported by various learning resources"
,
"attributes"
:
[
{
"name"
:
"resource_type"
,
"type"
:
"enumeration"
,
"values"
:
[
"primary"
,
"supplementary"
,
"assessment"
]
,
"description"
:
"Type of resource support"
}
,
{
"name"
:
"effectiveness_rating"
,
"type"
:
"number"
,
"description"
:
"Resource effectiveness for this skill"
}
]
,
"business_justification"
:
"Enables mapping skills to learning materials"
,
"requirements_addressed"
:
[
"R-007"
,
"R-010"
]
}
]
,
"impact_analysis"
:
{
"organizational_model_changes"
:
[
{
"model_file"
:
"orgModel/01-skill-dev/domain-model.md"
,
"change_type"
:
"addition|modification|deprecation"
,
"description"
:
"Add SkillProgression entity and Skills Development Lifecycle pattern"
,
"affected_sections"
:
[
"Entities"
,
"Workflows"
]
,
"backward_compatibility"
:
true
,
"migration_required"
:
false
}
]
,
"project_benefits"
:
[
{
"benefit"
:
"Improved skill tracking granularity"
,
"measurement"
:
"Progression milestones tracked per team member"
,
"stakeholder_value"
:
"Managers get detailed development insights"
}
]
,
"implementation_requirements"
:
[
{
"requirement"
:
"Data model extensions"
,
"effort"
:
"2-3 days"
,
"dependencies"
:
[
"Database schema updates"
,
"API modifications"
]
}
]
}
}
**Justification**
**Requirements Evidence**
## Concept Proposals
### 🆕 New Entity Proposals
#### PROP-001: SkillProgression Entity
**Purpose**
**Domain Area**
**Fills Gap**
**Core Attributes**
-
`progression_id`
-
`current_level`
-
`start_date`
-
`milestones`
**Key Relationships**
-
**TeamMember**
_to (many-to-one): Each progression belongs to one team member
- **Skill** ← tracks (many-to-one): Each progression tracks one specific skill
**Business Value** :
- ✅ Enables systematic tracking of learning progress
- ✅ Clear visibility into individual development
- ✅ Data-driven skill planning capabilities
- ✅ Progress reporting and analytics
**Requirements Addressed** :
- **R-005** : Track individual skill development → *Provides complete progression tracking*
- **R-012** : Generate progress reports → *Enables milestone-based reporting*
**Implementation Considerations** :
- **Integration** : Extends existing TeamMember and Skills entities
- **Data Needs** : Historical assessments, milestone definitions
- **Potential Conflicts** : ⚠️ Overlaps with Assessment entity
- *Resolution*: SkillProgression aggregates multiple Assessments over time
**Risk Assessment** : 🟢 Low Risk
- Implementation complexity: Low
- Organizational impact: Medium
- Mitigation: Pilot with single team, gradual rollout
### 🔄 New Pattern Proposals
#### PATP-001: Skills Development Lifecycle
**Pattern Type** : Workflow Pattern
**Purpose** : Standard workflow for skill acquisition and mastery
**Fills Gap** : PAT-001 (Missing Development Lifecycle)
**Lifecycle Phases** :
1. **🔍 Discovery Phase**
- *Purpose*: Identify skill needs and learning opportunities
- *Entities*: TeamMember, Skill, LearningResource
- *Activities*: Skill gap assessment, Learning path planning
2. **📚 Development Phase**
- *Purpose*: Active learning and skill building
- *Entities*: SkillProgression, Assessment, LearningResource
- *Activities*: Learning completion, Progress tracking
3. **✅ Validation Phase**
- *Purpose*: Demonstrate and validate skill mastery
- *Entities*: Assessment, Skill, TeamMember
- *Activities*: Skill demonstration, Competency validation
4. **🎯 Application Phase**
- *Purpose*: Apply skills in real work contexts
- *Entities*: TeamMember, Skill, WorkActivity
- *Activities*: Skill application, Performance monitoring
**Business Value** : Provides standardized approach to skill development across organization
**Implementation Impact** : Requires workflow definition and training materials
**Requirements Supported** : R-003, R-008, R-015
### 🔗 New Relationship Proposals
#### RELP-001: Skill ↔ LearningResource
**Relationship** : Skill **supported_by** LearningResource (many-to-many)
**Purpose** : Connect skills to their supporting learning materials
**Fills Gap** : RELA-001 (Missing Skill-Resource Connection)
**Relationship Attributes** :
- `resource_
-
`effectiveness_rating`
**Business Justification**
**Requirements Addressed**
## Impact Analysis
### 📋 Organizational Model Changes
#### orgModel/01-skill-dev/domain-model.md
**Change Type**
**Changes**
-
-
-
**Migration Required**
### 📈 Project Benefits
### ⚙️ Implementation Requirements
**Total Estimated Effort**
**Critical Path**
## Risk Assessment & Mitigation
### 🔴 Implementation Risks
### 🟢 Success Factors
-
**Clear stakeholder value**
-
**Backward compatibility**
-
**Incremental implementation**
-
**Requirements alignment**
## Recommendations
### 🎯 High Priority Actions
1.
**Approve SkillProgression Entity**
-
-
-
2.
**Define Skills Development Lifecycle**
-
-
### 🔄 Implementation Sequencing
**Phase 1**
-
-
**Phase 2**
-
-
**Phase 3**
-
-
**Next Steps**
**Approval Required**
**Generated**
이 저장소의 다른 Skills Trace how changes at one EDPS hierarchy level propagate to parent and child levels. Given a boundary restructuring, participant rename, or requirement modification, this skill identifies all affected artifacts across the full hierarchy tree, generates a prioritised impact report, and supports what-if mode so proposed changes can be evaluated without being applied. Use when a user wants to understand the blast radius of a hierarchy or requirement change, trace a requirement to all implementing artifacts, or run a pre-flight check before executing a hierarchy modification.
diagram-generatecollaboration Generate Mermaid collaboration diagrams embedded in markdown, visualizing system interactions and workflows from domain concepts and requirements. Creates sequence diagrams, flowcharts, class diagrams, and interaction patterns with traceability links to source requirements. This skill is the single authoritative source for boundary validation rules VR-1 through VR-4 and their check algorithms; other skills (e.g., edps-compliance) delegate VR checking to this skill rather than reimplementing it.
Automate generation of process documentation at each hierarchy level following organizational standards. Auto-generates main.md (with hierarchy navigation and breadcrumb), process.md (level-appropriate activity diagram and description), collaboration.md (EDPS-compliant sequencing with box boundaries and participant stereotypes), and domain-model.md (entities scoped to the boundary). Use when a new process folder has been created (e.g., after hierarchy-management decomposition), when existing docs need to be regenerated from collaboration.md, or when a user asks to "document a process", "generate docs", "regenerate documentation", or "fill in the templates" for a hierarchy level.
