process-scopemin

Identifies minimum viable scope for requirements, helping prioritize essential features and define MVP boundaries. Analyzes requirements to classify core vs. optional features and produces scoped requirement sets for iterative development.

Jump to install

Repository: zhongadamwang/AI_Slowcooker
Last source activity: March 17, 2026 at 13:40
Detected SKILL.md language: English
Stars: 0
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/zhongadamwang/AI_Slowcooker --skill process-scopemin

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

change-impact-analysis

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.

2026-04-03

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.

2026-04-03

documentation-automation

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.

2026-04-03

View all from this repository

name	process-scopemin
description	Identifies minimum viable scope for requirements, helping prioritize essential features and define MVP boundaries. Analyzes requirements to classify core vs. optional features and produces scoped requirement sets for iterative development.
license	MIT

Process Scope Minimization

Transforms comprehensive requirements into minimum viable product (MVP) scope by analyzing business value, dependencies, and implementation complexity to identify core features and establish iterative development boundaries.

Intent

Identify the minimum viable product (MVP) scope from a comprehensive requirements set by classifying features as core, enhancing, or optional based on business value, inter-feature dependencies, and implementation complexity. Produces scoped requirement sets for iterative delivery planning.

Inputs

Requirements: Raw requirements text, document, or requirements.json/requirements.md (from requirements-ingest)
Project ID: project_id
Optional: goals.json from goals-extract — used to weight business-value scoring

Outputs

outputs/projects/{project_id}/Analysis/scope-analysis.md — Scope analysis report with MVP recommendation (primary, for downstream skills)
outputs/projects/{project_id}/Analysis/scope-analysis.json — Structured scope classifications (machine processing)

# Minimum Viable Scope Analysis **Project**: PROJECT-001 **Source**: requirements.md **Generated**: 2026-02-15T10:30:00Z **Analysis Method**: Business Value + Dependency + Complexity Assessment ## Executive Summary **MVP Definition**: [Brief description of the minimum viable product] **Core Features Count**: X features identified as essential **Enhancement Features**: Y features for post-MVP phases **Optional Features**: Z features for future consideration **Estimated MVP Effort**: [Time/resource estimate] ## Core Features (MVP Essential) ### Feature: [Feature Name] - **Business Value**: [High/Medium/Low] - [Justification] - **Technical Complexity**: [High/Medium/Low] - **Dependencies**: [List of prerequisite features] - **User Impact**: [Critical functionality description] - **Risk of Exclusion**: [What happens if not included in MVP] ## Enhancement Features (Post-MVP Phase 1) ### Feature: [Feature Name] - **Business Value**: [High/Medium/Low] - [Justification] - **Technical Complexity**: [High/Medium/Low] - **Dependencies**: [List of prerequisite features] - **Enhancement Rationale**: [Why this builds on MVP] - **Target Release**: [Suggested phase/timeline] ## Optional Features (Future Consideration) ### Feature: [Feature Name] - **Business Value**: [High/Medium/Low] - [Justification] - **Technical Complexity**: [High/Medium/Low] - **Nice-to-Have Rationale**: [Why this is optional] - **Potential ROI**: [Return on investment analysis] ## Feature Prioritization Matrix | Feature | Business Value | Technical Complexity | Dependencies | MVP Category | |---------|----------------|---------------------|--------------|--------------| | [Name] | [H/M/L] | [H/M/L] | [List/None] | [Core/Enhance/Optional] | ## MVP Roadmap ### Phase 0 - Foundation - [Core infrastructure features] - [Essential service foundations] ### Phase 1 - MVP Launch - [Minimum viable feature set] - [Core user workflows] ### Phase 2 - Enhancement - [First enhancement features] - [User experience improvements] ### Phase 3 - Expansion - [Advanced features consideration] - [Platform scaling capabilities] ## Scope Boundaries ### In Scope (MVP) - [Clearly defined included functionality] - [Core user journeys supported] - [Essential integrations] ### Out of Scope (MVP) - [Explicitly excluded functionality] - [Deferred advanced features] - [Future integration considerations] ## Risk Assessment ### High Priority Risks - [Risks that could impact MVP viability] - [Mitigation strategies] ### Medium Priority Risks - [Risks that could delay enhancement phases] - [Monitoring approaches] ## Success Criteria ### MVP Launch Success - [Measurable criteria for MVP success] - [User adoption metrics] - [Business value validation] ### Enhancement Phase Success - [Criteria for proceeding to enhancement features] - [Performance and usage thresholds] ## Recommendations ### Immediate Actions 1. [Priority development recommendations] 2. [Resource allocation suggestions] 3. [Risk mitigation priorities] ### Future Considerations 1. [Long-term strategic recommendations] 2. [Technology evolution planning] 3. [Market expansion opportunities] --- **Traceability**: Requirements tracked to original specifications **Review Date**: [Scheduled scope review date] **Stakeholder Approval**: [Pending/Approved status]

{ "metadata": { "project_id": "PROJECT-001", "source_file": "requirements.md", "generated_timestamp": "2026-02-15T10:30:00Z", "analysis_method": "business_value_dependency_complexity", "skill_version": "1.0.0" }, "mvp_summary": { "definition": "Brief MVP description", "core_features_count": 5, "enhancement_features_count": 8, "optional_features_count": 12, "estimated_effort": "3-4 months" }, "features": [ { "id": "FEAT-001", "name": "Feature Name", "category": "core|enhancement|optional", "business_value": { "score": "high|medium|low", "justification": "Value proposition explanation" }, "technical_complexity": { "score": "high|medium|low", "implementation_notes": "Technical considerations" }, "dependencies": [ "FEAT-002", "FEAT-003" ], "user_impact": "Impact description", "priority_score": 85, "phase_assignment": "mvp|phase1|phase2|future" } ], "roadmap": { "phase0_foundation": ["FEAT-001", "FEAT-002"], "phase1_mvp": ["FEAT-003", "FEAT-004"], "phase2_enhancement": ["FEAT-005", "FEAT-006"], "phase3_expansion": ["FEAT-007", "FEAT-008"] }, "scope_boundaries": { "in_scope": [ "Core functionality description", "Essential user workflows" ], "out_of_scope": [ "Advanced features deferred", "Future integrations" ] }, "risks": [ { "id": "RISK-001", "priority": "high|medium|low", "description": "Risk description", "impact": "Impact on scope", "mitigation": "Mitigation strategy" } ], "success_criteria": { "mvp_launch": [ "User adoption target", "Business value metric" ], "enhancement_phase": [ "Performance threshold", "Feature usage metric" ] }, "traceability": [ { "feature_id": "FEAT-001", "source_requirements": ["REQ-001", "REQ-003"], "justification": "Traceability explanation" } ] }

process-scopemin

Install options

Review the source files

Process Scope Minimization

Intent

Inputs

Outputs

Process Scope Minimization

Intent

Inputs

Outputs

Core Function

Usage

Output Schema

Analysis Methodology

1. Feature Classification Algorithm

2. Business Value Assessment

3. Dependency Analysis

4. Complexity Evaluation

5. MVP Boundary Definition

Implementation Strategy

Phase-Based Development

Iterative Refinement Process

Integration Points

Quality Assurance

Validation Checklist

Success Metrics

process-scopemin

Source facts

Install options

Review the source files

More from this repository

More from this repository

Process Scope Minimization

Intent

Inputs

Outputs

Process Scope Minimization

Intent

Inputs

Outputs

Core Function

Usage

Output Schema

Analysis Methodology

1. Feature Classification Algorithm

2. Business Value Assessment

3. Dependency Analysis

4. Complexity Evaluation

5. MVP Boundary Definition

Implementation Strategy

Phase-Based Development

Iterative Refinement Process

Integration Points

Quality Assurance

Validation Checklist

Success Metrics