skills.rest
TalonT-Org
TalonT-OrgOFFICIAL
Explore all skills by this author →
GitHub

make-req

Decompose high-level tasks into structured, independently plannable requirements.

5|1|Updated Feb 18, 2026
Search Tags:#planning#task management#requirements#decomposition#feature breakdown
One-click install
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill make-req
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-req
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/.claude/skills/make-req
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill make-req

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill transforms complex tasks, plans, or feature descriptions into a structured set of verifiable requirements, making them easier to understand and plan for implementation.

Core Features & Use Cases

  • Decomposition: Breaks down large objectives into smaller, manageable requirements.
  • Structured Output: Organizes requirements into logical groups with clear backgrounds.
  • Use Case: You have a high-level feature request for a new user authentication system. This Skill can decompose it into specific requirements for login, registration, password reset, and role management, each grouped for independent planning.

Quick Start

Use the make-req skill to decompose the task 'Implement user profile editing'.

Frequently Asked Questions about make-req

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

FAQPage Schema
How do I break down a feature request into independently plannable requirements?▼

To break down a feature request into independently plannable requirements, decompose high-level tasks or feature descriptions into a structured set of verifiable requirements grouped logically for implementation.

Can I use task decomposition for complex software project planning?▼

Yes, you can use task decomposition for software project planning. It transforms complex plans or feature descriptions into a structured set of verifiable requirements tailored specifically for project planning scenarios.

What is the best way to structure requirements for a new user authentication system?▼

The best way to structure requirements for an authentication system is decomposing the objective into specific, independently plannable requirements for login, registration, password reset, and role management.

Do I need a codebase context for feature breakdown and requirement definition?▼

Yes, you need codebase context for feature breakdown. The requirement definition process requires subagent verification of source material against your codebase context to ensure accuracy.

When should I not use structured task decomposition for project planning?▼

You should not use structured task decomposition when dealing with simple, single-step tasks that require no independent planning, as the overhead of grouping verifiable requirements provides no benefit.

Related Skills

Explore More Product & Management Skills→
nprbstnprbst
4

speck-help

Interpret Speck artifacts to answer questions about specs, plans, and tasks.

Community
Basic
achmfachmf

plan-writing

Create structured, verifiable task plans for software development projects.

Community
Intermediate
tygwantygwan
1

phase

Coordinate project phases and track their status with automated updates.

Community
Advanced
royhenengelroyhenengel

plan

Generate spec-driven implementation plans for software development tasks.

Community
Intermediate