needs-tasks

Generate phased implementation task lists from feature designs and user stories.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/provenimpact/proven-needs --skill needs-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: needs-tasks
Source: https://github.com/provenimpact/proven-needs/tree/main/skills/needs-tasks
Command: npx skills add https://github.com/provenimpact/proven-needs --skill needs-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product and engineering teams convert a feature request into a structured, phased task list that aligns with design, stories, and specs to accelerate delivery.

Core Features & Use Cases

  • Derives tasks from design, stories, and specs when a design exists
  • Derives tasks directly from user stories when no design exists
  • Organizes tasks into sequential phases with parallelism markers and traceability to origins
  • Generates a docs/features/<slug>/tasks.adoc file with versioning, status, and traceability

Quick Start

Provide a phased, traceable task plan for the current feature by analyzing its design, stories, and constraints.

Frequently Asked Questions about needs-tasks

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

FAQPage Schema
How do I generate a phased task list from feature design and user stories?

Generate a phased task list by analyzing documented feature design, user stories, and constraints to derive sequential implementation tasks with parallelism markers and traceability to their origins.

Can I derive implementation tasks from user stories when no design documentation exists?

Yes, when no design exists, implementation tasks are derived directly from user stories, organizing them into sequential phases while maintaining traceability to the original story requirements.

What is the best way to organize feature delivery tasks into phases with traceability?

Organize feature delivery tasks into sequential phases with parallelism markers and traceability fields by generating a structured tasks.adoc file that links each task back to its design or story origin.

How does agile phase management handle task versioning and status tracking?

Agile phase management handles task versioning and status by generating a tasks.adoc file that specifies required inputs, outputs, and constraints, ensuring consistent task documentation with version and status fields.

Do I need documented specs to create a traceable task plan for feature delivery?

You need documented user stories or feature design specs to create a traceable task plan, as the tool requires these inputs to derive organized phases and maintain traceability to origins.

When should I not use automated task derivation for feature planning?

You should avoid automated task derivation when a feature lacks both documented design and user stories, as the tool requires these inputs to generate phased, traceable implementation plans.