sdd:add-task

Generate standardized draft task files from user input for software development workflows.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/fockus/claude-skill-build --skill sdd-add-task-fockus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd:add-task
Source: https://github.com/fockus/claude-skill-build/tree/main/skills/sdd-add-task
Command: npx skills add https://github.com/fockus/claude-skill-build --skill sdd-add-task-fockus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting precise, ready-to-implement task specifications from user input to accelerate task planning and reduce ambiguity.

Core Features & Use Cases

  • Automatically parses user input to generate a concise, action-oriented task title.
  • Validates task type and naming, ensuring unique, consistent task file names across statuses.
  • Prepares a draft file in .specs/tasks/draft/ ready for handoff to the todo pipeline.

Quick Start

Create a draft task file under .specs/tasks/draft/ that captures the user's task description and metadata.

Frequently Asked Questions about sdd:add-task

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

FAQPage Schema
How do I create standardized draft task files from user requests?

Generating draft task files from user requests involves parsing input to create an action-oriented title and validating task types to ensure consistent naming. The skill enforces a fixed file structure under .specs/tasks/draft/ to reduce ambiguity in task planning.

What is the best way to reduce ambiguity in software task planning?

Reducing ambiguity in task planning is achieved by drafting precise, ready-to-implement task specifications with a standardized file format. This approach enforces unique naming, lifecycle tracking, and consistent task types before any work begins.

How does automated task file generation work for draft specs?

Automated task file generation works by parsing raw user input to produce a standardized draft task file with a concise title. It validates task types, ensures unique naming across statuses, and records dependencies to accelerate the planning workflow.

Do I need a specific directory structure to automate task drafting?

A specific directory structure is required for task drafting. The process prepares draft files in the .specs/tasks/draft/ directory, enforcing a fixed file structure that ensures unique naming and seamless handoff to the todo pipeline.

Can I track task dependencies when generating draft task files?

You can track task dependencies when generating draft task files. If dependencies are provided in the user input, the skill records them within the standardized draft file to support lifecycle tracking across the software development workflow.

When should I use an automated draft task generator over manual task entry?

An automated draft task generator should be used over manual entry when transitioning tasks from draft to todo in software development workflows. It ensures consistent naming, validates types, and enforces a fixed file structure that manual processes often lack.