skills.rest
zhongadamwang
zhongadamwangCOMMUNITY
Explore all skills by this author →
GitHub

process-scopemin

Classify requirements into core, enhancement, or optional and generate Markdown and JSON scope maps.

Updated Feb 21, 2026
Search Tags:#requirements#analysis#roadmap#prioritization#mvp#scope#feature-classification
One-click install
npx skills add https://github.com/zhongadamwang/CCAGA --skill process-scopemin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-scopemin
Source: https://github.com/zhongadamwang/CCAGA/tree/main/.github/skills/process-scopemin
Command: npx skills add https://github.com/zhongadamwang/CCAGA --skill process-scopemin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies the minimum viable scope from comprehensive requirements, helping teams prioritize essential features and clearly define MVP boundaries to accelerate iterative development.

Core Features & Use Cases

  • Classifies requirements into core, enhancement, and optional features based on business value, dependencies, and complexity.
  • Generates both human-readable Markdown scope analysis and machine-readable JSON scope map for downstream tooling.
  • Produces project-scoped outputs (scope-analysis.md and scope-analysis.json) under outputs/projects/{project_id}/Analysis for traceability and reuse.

Quick Start

Provide a requirements document and a project_id to generate the scope analysis report and a structured JSON scope map.

Frequently Asked Questions about process-scopemin

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

FAQPage Schema
How do I prioritize requirements and define an MVP scope for my project?▼

To prioritize requirements and define an MVP scope, you classify features based on business value, dependencies, and complexity. This identifies minimum viable boundaries by categorizing features into core, enhancement, or optional tiers for iterative development.

What is the best way to map feature dependencies for a roadmap?▼

Mapping feature dependencies for a roadmap involves analyzing requirements to classify features into core, enhancement, or optional categories. This ensures traceability for project planning by producing a structured scope map that outlines essential boundaries.

Can I generate a machine-readable JSON scope map from my requirements document?▼

Yes, you can generate a machine-readable JSON scope map from a requirements document. Providing the requirements and a project identifier produces both a Markdown scope analysis and a structured JSON scope map for downstream tooling integration.

How do I classify features into core, enhancement, and optional categories?▼

You classify features into core, enhancement, and optional categories by evaluating their business value, dependencies, and complexity. This classification identifies the minimum viable scope required to accelerate iterative development.

Do I need a project_id to analyze my MVP scope?▼

Yes, you need a project_id to analyze your MVP scope. The identifier is required to produce project-scoped outputs, specifically generating the scope-analysis.md and scope-analysis.json files under the outputs/projects/{project_id}/Analysis directory.

Related Skills

Explore More Product & Management Skills→
martinffxmartinffx
39

spec:product

Document product requirements and define feature scope from discovery interviews.

Community
Advanced
slgoodrichslgoodrich
121

prioritization-methods

Prioritize features using RICE, ICE, MoSCoW, Kano, and weighted scoring frameworks.

Community
Basic
edwardmonteiroedwardmonteiro

delivery.roadmap

Translate strategy into a sequenced delivery roadmap with risks and stakeholder communication.

Community
Basic
martinffxmartinffx
39

atelier-spec-product

Conduct discovery interviews to define feature scope and requirements.

Community
Intermediate