agent

Execute ClickUp tickets end-to-end with API and Git operations.

1|Updated Sep 17, 2025
One-click install
npx skills add https://github.com/mpazaryna/agentic-factory --skill agent-mpazaryna
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent
Source: https://github.com/mpazaryna/agentic-factory/tree/main/pm/clickup/skills/agent
Command: npx skills add https://github.com/mpazaryna/agentic-factory --skill agent-mpazaryna

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the entire lifecycle of a ClickUp ticket, from fetching and planning to implementation, testing, merging, and closing, eliminating the need for human checkpoints.

Core Features & Use Cases

  • Full Ticket Automation: Handles fetching ticket details, planning the work, implementing code changes, running tests, creating pull requests, merging them, and finally closing the ticket.
  • Autonomous Operation: Designed to run without requiring user intervention at any stage, escalating only when absolutely necessary.
  • Use Case: When a user wants a specific task or bug fix on ClickUp to be completed entirely without their direct involvement, this agent can be invoked.

Quick Start

Use the agent skill to autonomously complete the ClickUp ticket with ID '12345'.

Frequently Asked Questions about agent

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

FAQPage Schema
How do I automate ClickUp ticket execution end-to-end without manual checkpoints?

Automating ClickUp ticket execution requires an agent that fetches ticket details, plans work, implements code, runs tests, creates PRs, merges, and closes tickets autonomously. You need a ClickUp API key and project context in CONTEXT.md for build convention adherence.

Do I need a ClickUp API key to autonomously execute developer workflow tasks?

Yes, autonomous developer workflow execution requires a ClickUp API key to fetch ticket details and manage status transitions. You also need project context provided via a CONTEXT.md file to ensure code changes follow build and repository conventions.

How does an autonomous agent handle git operations and pull requests for ClickUp tasks?

An autonomous agent handles git operations by implementing code changes locally, running tests, creating pull requests, merging them, and updating the ClickUp ticket status via API calls, entirely eliminating the need for manual human intervention during the lifecycle.

What's the best way to ensure autonomous code execution follows my project conventions?

To ensure autonomous code execution follows project conventions, provide a CONTEXT.md file detailing build instructions and coding standards. The agent reads this context alongside the ClickUp ticket details to plan and implement compliant code changes.

Can I fully automate bug fix lifecycle management from ClickUp to Git merge?

Yes, you can fully automate the bug fix lifecycle from ClickUp to Git merge. The agent processes the ticket, writes the fix, runs tests, creates the PR, merges it, and closes the ClickUp ticket without requiring direct user involvement.