sdd-add-task

Create draft task files in `.specs/tasks/draft/` with type and filename.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Gamezar/opencode-cek --skill sdd-add-task-gamezar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-add-task
Source: https://github.com/Gamezar/opencode-cek/tree/main/plugins/sdd/skills/sdd-add-task
Command: npx skills add https://github.com/Gamezar/opencode-cek --skill sdd-add-task-gamezar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the initial creation of task files for Specification-Driven Development, ensuring tasks are properly formatted and categorized from the outset.

Core Features & Use Cases

  • Task File Generation: Creates draft task files in the .specs/tasks/draft/ directory.
  • Automated Structuring: Automatically assigns a title, type (feature, bug, etc.), and file name based on user input.
  • Use Case: When a new requirement or bug is identified, use this Skill to quickly generate a well-structured task file, ready for further refinement and tracking.

Quick Start

Create a new task file for adding user authentication to the system.

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 draft task files for Specification-Driven Development?

To create draft task files for Specification-Driven Development, you parse user input to generate an action-oriented title, determine the issue type, and save it to the `.specs/tasks/draft/` directory using a standardized `<short-name>.<issue-type>.md` file naming convention.

What task types are supported when generating issues for an SDD workflow?

Supported task types for SDD workflow issue generation include feature, bug, refactor, test, docs, chore, and ci. The system parses your input to automatically categorize the requirement and assign the appropriate issue type to the file name.

How do I structure a new development task file for proper issue tracking?

To structure a development task file for issue tracking, the system ensures a proper directory structure by generating a file with an action-oriented title and a unique `<short-name>.<issue-type>.md` file name within the `.specs/tasks/draft/` directory.

When do I need to generate a structured task file for development workflows?

You need to generate a structured task file when a new requirement or bug is identified. This ensures tasks are properly formatted, categorized by issue type, and ready for further refinement and tracking within your development workflow.

Does the task generation process require any external dependencies?

No, the task generation process requires no external dependencies. It solely relies on internal scripts to parse input, construct the unique file name, and ensure the correct `.specs/tasks/draft/` directory structure for your task management workflow.