new-task

Decompose vague requirements into STV-based specs and trace artifacts.

36|3|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/2lab-ai/oh-my-claude --skill new-task-2lab-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-task
Source: https://github.com/2lab-ai/oh-my-claude/tree/main/plugins/stv/skills/new-task
Command: npx skills add https://github.com/2lab-ai/oh-my-claude --skill new-task-2lab-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms vague user requirements into concrete, STV-based specs and traced artifacts to guide implementation.

Core Features & Use Cases

  • Decompose vague requirements into a spec (stv:spec) and a trace (stv:trace)
  • Produce implementable work artifacts and task lists for downstream work
  • Use in product ideation, feature scoping, and architectural planning to clarify ambiguity

Quick Start

Provide a vague request and let this skill orchestrate STV spec and trace generation.

Frequently Asked Questions about new-task

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

FAQPage Schema
How do I decompose vague product requirements into actionable specs?

To decompose vague product requirements into actionable specs, you break down ambiguous user prompts into STV-based specifications and trace artifacts. This translates unclear requests into concrete tasks suitable for downstream work automation and architectural planning.

What is requirement decomposition and when do I need it?

Requirement decomposition is the process of transforming ambiguous user requests into structured STV specs and traced artifacts. You need it during product ideation, feature scoping, and architectural planning to clarify vague requests and guide implementation.

How do I generate a trace for feature scoping workflows?

Generating a trace for feature scoping workflows requires orchestrating STV spec and trace generation from a vague request. This produces traced artifacts that map decomposed requirements to concrete implementation tasks for downstream work automation.

Can I turn ambiguous user prompts into task lists for work automation?

Yes, you can turn ambiguous user prompts into task lists for work automation by decomposing them into STV-based specs. This produces a summarized task list and trace artifacts designed to guide downstream implementation automatically.

What's the best way to structure specs for architectural planning?

The best way to structure specs for architectural planning is using STV-based specifications with trace artifacts. This approach clarifies ambiguity by decomposing vague requirements into concrete tasks and traces that guide implementation.