skills.rest
Seok-Ryu
Seok-RyuCOMMUNITY
Explore all skills by this author →
GitHub

sdd-classify

Classify user work requests into change type, starting point (PRD/SPEC/PLAN/TASK), and required scope.

Updated Aug 23, 2026
Search Tags:#workflow#requirements#sdd#classify#task-plans
One-click install
npx skills add https://github.com/Seok-Ryu/spec-driven-flow-with-agents --skill sdd-classify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-classify
Source: https://github.com/Seok-Ryu/spec-driven-flow-with-agents/tree/main/.claude/skills/sdd-classify
Command: npx skills add https://github.com/Seok-Ryu/spec-driven-flow-with-agents --skill sdd-classify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify user work requests to determine the appropriate starting document (PRD/SPEC/PLAN/TASK) and the required scope, enabling faster and more accurate workflow initiation.

Core Features & Use Cases

  • Determine the change type (Feature, Enhancement, Bug fix, Hotfix, Refactoring) from user input.
  • Decide the starting point (PRD, SPEC, PLAN, TASK, or none) and the required documentation structure.
  • Output clear next steps and document storage location to keep the workflow aligned.

Quick Start

Provide the task details (e.g., Jira ticket or user request) to begin the classification workflow.

Frequently Asked Questions about sdd-classify

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

FAQPage Schema
How do I determine the right starting document for a software task request?▼

To determine the right starting document for a software task request, you classify the change type—such as a feature, bug fix, or refactor—to decide whether to begin with a PRD, SPEC, PLAN, or TASK.

What is the best way to classify work requests for bug fixes versus new features?▼

Classifying work requests for bug fixes versus new features involves applying decision criteria to user input to identify the change type and required scope, which then clarifies the necessary starting documentation and next steps.

Can I use task details from a Jira ticket to initiate the workflow classification process?▼

Yes, you can use task details from a Jira ticket or direct user request to initiate the classification workflow, which evaluates the input to determine the appropriate starting point and required documentation structure.

How do I know if a software enhancement requires a PRD or just a SPEC document?▼

Knowing if a software enhancement requires a PRD or a SPEC document depends on applying enforced decision criteria to the request, which evaluates the change type and scope to output clear next steps and document storage location.

When do I need to start my software refactoring workflow with a PLAN instead of a TASK?▼

You need to start a software refactoring workflow with a PLAN instead of a TASK when the classification process determines the change scope requires broader planning documentation to maintain workflow alignment and traceability.

Related Skills

Explore More Software Engineering Skills→
qa-amanqa-aman
19

jira-ticket-creator

Parse notes, user stories, or lists into structured Jira tickets via REST API.

Community
Advanced
okwindsokwinds
50

prd-to-engineering-spec

Transform a PRD into an implementation-ready engineering specification with architecture, data modeling, API design, security, deployment, and testing.

Community
Advanced
cuiosscuioss
4

planning

Create and maintain TODO.adoc, ROADMAP.adoc, and BACKLOG.adoc with task traceability.

Official
Intermediate
CloudChefCloudChef
15

skill-vetter

Assess AI skills for security risks and generate a structured vetting report.

Official
Advanced