
Security News
How Enterprise Security Is Adapting to AI-Accelerated Threats
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.
A powerful extension that scans documentation folders for task information, generates comprehensive task documentation using Claude Sonnet LLM, and uploads tasks directly to your project management tools.
Compatible with: VS Code, Cursor, and other VS Code-compatible editors
.cursorrulesTask ID: <ID> in documentation files[Force] tag for repeated uploads[Image] tag to generate Mermaid diagrams automaticallyMaximize the benefit of Task Connector by integrating it with your AI coding assistant. Create a seamless workflow where your AI assistant generates task documentation files, and Task Connector automatically processes and uploads them to your project management tool.
Configure your AI assistant with these rules:
documentation/, docs/, tasks/).md files)Task ID: FEAT-123)For Cursor users who want automatic documentation generation, you can optionally add these rules to your .cursorrules file in your project root: (documentation is in the root folder in this example)
- always go through all the '.md' files in 'documentation' folder to understand project context.
- create the '.md' documents in the 'documentation' folder in the root folder.
Note: This configuration is optional and only needed if you want Cursor to automatically generate task documentation. You can still use Task Connector without these rules by manually creating task files.
Alternative Cursor Configuration: You can also add these rules directly in Cursor's settings:
Cmd/Ctrl + ,)For VS Code with GitHub Copilot users, configure Copilot with these guidelines:
Create a .github/copilot-instructions.md file in your project root:
# Copilot Instructions for Task Connector
When creating task documentation:
- Always create files in the `documentation/` folder
- Use markdown format (.md files)
- Include Task ID at the top: `Task ID: FEAT-123`
- Avoid emojis in task documentation
- Break down tasks into clear steps
- Use proper markdown formatting
Reference this file when asking Copilot to create tasks:
.github/copilot-instructions.md"For other AI coding assistants (Claude Desktop, ChatGPT, etc.), provide these instructions:
documentation/ folder"Ask your AI assistant to create a task:
AI creates a file (e.g., documentation/user-auth.md):
Task ID: AUTH-001
# User Authentication Implementation
Implement secure user authentication system...
Task Connector processes it:
Cmd/Ctrl + Shift + P → "Scan Documentation Folder"Result: Task appears in your project management tool with full documentation, architecture diagrams, and acceptance criteria!
✅ No manual task creation - AI generates structured task files
✅ Consistent format - All tasks follow the same template
✅ Automatic context - AI reads existing tasks to maintain consistency
✅ One-click sync - Single command uploads everything to your project management tool
✅ Version control - Task documentation is tracked in Git
All supported editors can install Task Connector from their respective marketplaces:
Installation Steps:
Ctrl+Shift+X)Configure the extension through your editor's settings:
Cmd/Ctrl + ,)Note: Settings work the same way across all supported editors (VS Code, Cursor, etc.)
taskConnector.documentationDirectory""/Users/username/Projects/MyProject/docsHow to Configure Per-Project (Recommended Method):
Cmd/Ctrl + Shift + P to open Command Palette/Users/username/Projects/MyProject)docs or documentation, OR an absolute path.vscode/settings.json for this project onlyExample:
/Users/username/Projects/MyProjectdocs"taskConnector.documentationDirectory": "docs"Team Collaboration:
When you use relative paths (recommended):
.vscode/settings.json to version controlAlternative: Via Settings GUI
If you prefer using the Settings GUI:
Cmd/Ctrl + , to open SettingsImportant Notes:
API keys are now stored securely using VS Code's built-in secure storage mechanism. Use the following commands to set them:
Task Connector: Set Claude API Key commandTask Connector: Set ClickUp API Key commandTask Connector: Set ClickUp Configuration commandTask Connector: Clear All API Keys commandtaskConnector.clickupTaskIdType"native""native" or "custom"native: ClickUp-generated IDs (e.g., 86bnz7vkr)custom: Custom task IDs (e.g., PROJ-123)taskConnector.createTasksIfNotFoundfalse (disabled)Recommended Usage:
Task Connector: Configure Template from Command PaletteImportant: Each markdown file should contain only ONE task. The Task ID must be at the very top of the file.
In your markdown files, use the following format:
Task ID: FEAT-123
# Feature Implementation
This task involves implementing a new user authentication system.
The implementation should include login, logout, and session management.
Additional details about the implementation...
## Technical Requirements
- Use JWT tokens for session management
- Implement bcrypt for password hashing
## Testing Requirements
- Unit tests for all authentication flows
- Integration tests for OAuth providers
Optional Tags (place immediately after Task ID):
[Force] to upload this task every scan (instead of just once)[Uploaded] to skip this task during scanning (never upload)[Image] to generate a Mermaid architecture diagram[Force]By default, tasks are only uploaded once. After a successful upload, the extension tracks uploaded task IDs and skips them in subsequent scans. To force a task to be uploaded every time you scan, add the [Force] tag:
Task ID: FEAT-123
[Force]
# Feature Implementation
This task will be uploaded every time you run a scan, even if it was already uploaded before.
Formatting Requirements:
[Force] (capital F, lowercase o-r-c-e)Task ID: (within first 2 lines)[Force] not [ Force ] or [Force ][Force] not [Force] - update thisUse Cases for [Force] Tag:
Upload History Management:
Task Connector: Clear Upload History command[Uploaded]To prevent a task from being uploaded or processed during scanning, add the [Uploaded] tag:
Task ID: FEAT-123
[Uploaded]
# Feature Implementation
This task will be skipped during scanning and will never be uploaded to ClickUp.
Formatting Requirements:
[Uploaded] (capital U, lowercase p-l-o-a-d-e-d)Task ID: (within first 2 lines)[Uploaded] not [ Uploaded ] or [Uploaded ][Uploaded] not [Uploaded] - skip thisUse Cases for [Uploaded] Tag:
Important Notes:
[Uploaded] tag are completely skipped during scanning[Force] tag (if both are present, [Uploaded] wins)[Image]To include an architecture diagram in your task documentation, add the [Image] tag. Claude will automatically generate a Mermaid diagram:
Task ID: FEAT-123
[Image]
# Feature Implementation
Implement a new microservices architecture...
Formatting Requirements:
[Image] (capital I, lowercase m-a-g-e)Task ID: (within first 2 lines)[Image] not [ Image ] or [Image ][Force] tag (see below)You can use both [Force] and [Image] tags together. Place them on separate lines immediately after the Task ID (order doesn't matter):
Task ID: FEAT-123
[Force]
[Image]
# Feature Implementation
This task will be uploaded every scan AND include an architecture diagram.
OR
Task ID: FEAT-123
[Image]
[Force]
# Feature Implementation
Both orders work - the extension checks the first 2 lines after the Task ID.
Important Formatting Rules:
[Force], [Uploaded], or [Image] (case-sensitive)Task ID:[Force] not [ Force ][Force] - update this won't workTag Precedence:
[Uploaded] takes precedence over [Force] - if both are present, the task will be skipped[Force] and [Image] can be used together[Uploaded] and [Image] can be used together (task will be skipped but diagram generation is not relevant)Note: The [Force] and [Uploaded] tags are for internal tracking only and won't appear in the generated documentation sent to ClickUp. The [Image] tag instructs Claude to generate a Mermaid architecture diagram
Access commands through the Command Palette (Cmd/Ctrl + Shift + P) in any supported editor:
Customize your task documentation sections using the visual configurator:
Open the Configurator:
Cmd/Ctrl + Shift + P)Task Connector: Configure TemplateCustomize Sections:
Default Sections Available:
Security Benefits:
Cmd/Ctrl + Shift + P)Task Connector: Set Claude API Keysk-ant-)Currently supported: ClickUp
Get API Key:
pk_)Task Connector: Set ClickUp API Key commandGet Team ID:
https://app.clickup.com/12345678/home12345678Get List ID:
https://app.clickup.com/12345678/v/l/87654321Configure:
Task Connector: Set ClickUp Configuration commandTask ID: <ID> at the top of each fileTask ID: <ID> at the very top of the file.vscode/settings.json for workspace-specific configuration.cursorrules file is properly formatted and in the project rootFor issues and feature requests, please contact the development team. [zameerm@99x.io]
FAQs
Connect AI generated task documentation with project management tools
We found that 99x.task-connector demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CTO Ahmad Nassri discusses why supply chain attacks now target developer machines and what AI means for the future of enterprise security.

Security News
Learn the essential steps every developer should take to stay secure on npm and reduce exposure to supply chain attacks.

Security News
Experts push back on new claims about AI-driven ransomware, warning that hype and sponsored research are distorting how the threat is understood.