creates draft task file in .specs/tasks/draft/ with original user intent
51
40%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/sdd/skills/add-task/SKILL.mdYour role is to create a draft task file that exactly matches the user's request.
Create a task file in .specs/tasks/draft/ with:
.specs/tasks/draft/Run the folder creation script to create task directories and configure gitignore:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/create-folders.shThis creates:
.specs/tasks/draft/ - New tasks awaiting analysis.specs/tasks/todo/ - Tasks ready to implement.specs/tasks/in-progress/ - Currently being worked on.specs/tasks/done/ - Completed tasks.specs/scratchpad/ - Temporary working files (gitignored)Parse the user's request:
Clarify if ambiguous (only if truly unclear):
Create action-oriented title:
Determine type:
| Type | Use When |
|---|---|
feature | New functionality or capability |
bug | Something is broken or not working correctly |
refactor | Code restructuring without changing behavior |
test | Adding or updating tests |
docs | Documentation changes only |
chore | Maintenance tasks, dependency updates |
ci | CI/CD configuration changes |
Create short name from the task title:
add-validation-login-formForm file name: <short-name>.<issue-type>.md
add-validation-login-form.feature.mdfix-null-pointer-user-service.bug.mdrestructure-auth-module.refactor.mdadd-unit-tests-api.test.mdupdate-readme.docs.mdupgrade-dependencies.chore.mdadd-github-actions.ci.mdVerify uniqueness: Check .specs/tasks/draft/, .specs/tasks/todo/, .specs/tasks/in-progress/, and .specs/tasks/done/ for existing files with same name
Use Write tool to create .specs/tasks/todo/<short-name>.<issue-type>.md:
---
title: <ACTION-ORIENTED TITLE>
depends_on: <list of task files that this task depends on>
---
## Initial User Prompt
{EXACT user input as provided}
## Description
// Will be filled in future stages by business analyst.specs/tasks/draft/// ... placeholder as specified in the task file.Return to the orchestrator:
.specs/tasks/todo/add-validation-login-form.feature.md)task, bug, or featureFormat:
Created task file: .specs/tasks/draft/<name>.<type>.md
Title: <action-oriented title>
Type: <task|bug|feature>
Depends on: <list of task files that this task depends on>.specs/tasks/draft/, .specs/tasks/todo/, .specs/tasks/in-progress/, .specs/tasks/done/ exist.specs/tasks/draft/ with correct naming convention (<name>.<type>.md).feature.md, .bug.md, .refactor.md, .test.md, .docs.md, .chore.md, .ci.md)// Will be filled in future stages by business analystTest task (.specs/tasks/draft/add-unit-tests-auth.test.md):
---
title: Add unit tests for auth module
---
## Initial User Prompt
add tests for auth
## Description
// Will be filled in future stages by business analystBug with context (.specs/tasks/draft/fix-login-timeout.bug.md):
---
title: Fix login timeout on slow connections
---
## Initial User Prompt
users getting 504 errors on slow wifi
## Description
// Will be filled in future stages by business analystFeature request (.specs/tasks/draft/implement-dark-mode.feature.md):
---
title: Implement dark mode toggle
---
## Initial User Prompt
add dark mode to settings page
## Description
// Will be filled in future stages by business analystdedca19
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.