make-req

Decomposes task descriptions into structured, independently plannable requirement groups.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Trecek/useful-claude-skills --skill make-req-trecek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-req
Source: https://github.com/Trecek/useful-claude-skills/tree/main/.claude/skills/make-req
Command: npx skills add https://github.com/Trecek/useful-claude-skills --skill make-req-trecek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a task, plan, roadmap, or feature description into a structured set of requirements to guide independent planning and execution.

Core Features & Use Cases

  • Groups requirements into independently plannable sets with observable outcomes.
  • Uses subagents to understand source material and produce background context for each group.
  • Ensures requirements describe observable outcomes, not implementation details.

Quick Start

Provide a task description and let the skill decompose it into grouped, verifiable requirement sets.

Frequently Asked Questions about make-req

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

FAQPage Schema
How do I decompose a feature brief into independently plannable requirements?

Decomposing a feature brief into independently plannable requirements involves structuring a task description into grouped, verifiable sets with observable outcomes. The skill analyzes source material using subagents to produce background context for each requirement group.

What is the best way to break down a software roadmap into verifiable task sets?

Breaking down a software roadmap into verifiable task sets requires grouping requirements into independently plannable sets. This ensures requirements describe observable outcomes rather than implementation details, guiding separate execution phases.

How do I structure task decomposition to ensure requirements have observable outcomes?

Structuring task decomposition for observable outcomes requires analyzing source material and grouping requirements into verifiable sets. The process outputs results with background context for each group to guide independent planning.

Can I use subagents to analyze source material for requirements decomposition without modifying source code?

Yes, you can use subagents to analyze source material for requirements decomposition without modifying source code. The subagents read the provided task description and output the grouped requirements to a temporary directory.

Does this requirements decomposition approach generate implementation details for each task?

No, this requirements decomposition approach explicitly avoids generating implementation details. It structures requirements to describe only observable outcomes, ensuring each group remains independently plannable and verifiable.