clickup-spec

Creates, promotes, validates, and updates product items in a ClickUp workspace hierarchy.

Updated May 31, 2026
One-click install
npx skills add https://github.com/ithaloazevedo/pm-loadout --skill clickup-spec-ithaloazevedo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clickup-spec
Source: https://github.com/ithaloazevedo/pm-loadout/tree/main/.agents/skills/clickup-spec
Command: npx skills add https://github.com/ithaloazevedo/pm-loadout --skill clickup-spec-ithaloazevedo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product managers often write inconsistent, incomplete, or poorly structured items in ClickUp, making roadmaps hard to read and execution hard to track. This Skill structures and validates product items across the full hierarchy — Objective (OKR/KR) → Discovery Project → Delivery Project → subtasks — in the Vertical Tech ClickUp workspace, enforcing writing standards, correct folders, task types, and explicit confirmation before any external write. ## Core Features & Use Cases - Create items: Interactively diagnoses missing context, then drafts Objectives (OKR/KR), Discovery projects (Research, Prototype, Interview), or Delivery projects (Epic, Bug, Task, Correction) using templates with imperative titles, capability-based scope, and testable acceptance criteria. - Promote Discovery to Delivery: Converts a concluded Discovery into a new Delivery project in the correct squad folder, linking both items and suggesting narrative update comments. - Validate existing items: Audits a card on two independent axes — decision fidelity/evidence and artifact readiness — with checklists per item type and concrete improvement suggestions. - Post narrative updates: Drafts context → decision → next-step comments for lifecycle moments (approved, in delivery, bug in production) and confirms before posting. - Use case: A PM says "/clickup-spec create — structure a delivery project for repositioning facial KYC before the first deposit"; the Skill asks blocking questions, proposes a full spec following the Delivery template, and creates the task in the right squad Backlog only after approval. ## Quick Start Ask the assistant to run /clickup-spec create and describe the product item you want to structure in the ClickUp workspace.

Frequently Asked Questions about clickup-spec

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

FAQPage Schema
How do I create a product spec in ClickUp with this skill?▼

Run /clickup-spec create and describe your item. The skill diagnoses missing blocking information, drafts the item using the Objective, Discovery, or Delivery template, and creates the task in ClickUp only after your explicit approval.

How do I convert a discovery into a delivery project in ClickUp?▼

Use /clickup-spec promote followed by the task ID or partial name. The skill fetches the Discovery, checks its exit criteria, fills gaps, and creates a Delivery project in the correct squad folder with linked tasks between both items.

Does the skill write to ClickUp automatically without confirmation?▼

No. Three actions always require explicit confirmation: creating a task, setting prioritization custom fields, and posting comment updates. If the ClickUp connector is unavailable or offline mode is configured, the skill delivers the proposal in chat instead.

What is the difference between Discovery and Delivery items in this workflow?▼

Discovery covers research, prototyping in Figma, and open product or UX decisions with oriented scope. Delivery is execution only, with closed scope and testable acceptance criteria. Prototyping always belongs in Discovery, never Delivery.

Can the skill delete tasks or folders in ClickUp?▼

No. Deleting spaces, folders, or lists is prohibited. Task deletion requires double explicit confirmation with an irreversibility warning, and the skill always offers non-destructive alternatives like cancelling status or archiving.

Why does validation report two separate axes instead of one score?▼

The skill evaluates decision fidelity and evidence separately from artifact readiness, so a well-formatted card cannot hide a weak decision and a solid decision cannot mask an unexecutable item. Each axis gets its own rating and top finding.