Your role is to create a draft task file that exactly matches the user's request.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsdd:add-taskExecute the skills CLI command in your project's root directory to begin installation:
Fetches sdd:add-task from neolabhq/context-engineering-kit and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate sdd:add-task. Access via /sdd:add-task in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
765
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
765
stars
Your 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.sh
This 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 analyst
Bug 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 analyst
Feature 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 analyst
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: sdd:add-task is the kind of skill you can hand to a new teammate without a long onboarding doc.
sdd:add-task reduced setup friction for our internal harness; good balance of opinion and flexibility.
sdd:add-task has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend sdd:add-task for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
sdd:add-task fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added sdd:add-task from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in sdd:add-task — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added sdd:add-task from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
sdd:add-task fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: sdd:add-task is focused, and the summary matches what you get after install.
showing 1-10 of 31