Specs In Clickup
Productivityspecs-in-clickupSpecs In Clickup is an Agent Skill for productivity published in the Mr-Quin/danmaku-anywhere repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when finishing a brainstorm, writing a design spec, or producing an implementation plan in this project. Directs the output to ClickUp as a doc on the DA-XXX task instead of saving to the repo or local disk.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Mr-Quin/danmaku-anywhere/blob/HEAD/.claude/skills/specs-in-clickup/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/specs-in-clickup, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
specs-in-clickup
Brainstorm outputs, design specs, and implementation plans live as ClickUp docs linked from the owning DA-XXX task. Not in the repo (docs/superpowers/specs/, .specs/), not in agent auto-memory long-term. The ClickUp task is the single source of truth; repo-tracked specs go stale, local-only specs vanish with the worktree.
Prerequisites
- ClickUp MCP (
clickup_*tools) CLICKUP_DA_SPACE_IDset in the environment (the developer exports it in their shell, e.g.~/.zshenv; seeda-devstep 1)
If either is missing, stop and tell the human. Don't fall back to committing the spec to the repo. Never hardcode IDs in tracked files.
How to apply
After superpowers:brainstorming, superpowers:writing-plans, or anything that produces a spec/plan:
- Find or create the related ClickUp task.
da-devstep 1 does this. Note the DA-XXX ID. - Search for an existing doc before creating a new one.
clickup_searchwithfilters: { asset_types: ['doc'] }covers names and contents;clickup_get_task_commentscovers links posted to the task. Iterate viaclickup_update_document_pagerather than recreate. - Create the doc at space level. Tasks cannot be doc parents; list-level docs (
type: "6") surface as views inside the list. Resolve<space_id>from$CLICKUP_DA_SPACE_ID.clickup_create_document( name: "Spec: <topic>", parent: { id: <space_id>, type: "4" }, visibility: <project default>, create_page: false ) - Add the first page:
Multi-section specs use furtherclickup_create_document_page( document_id: <new doc id>, name: "Design", // or "Plan", "Notes" content: <markdown> )clickup_create_document_pagecalls. One doc per task; multiple pages within. - Link the doc to the task with a comment containing the URL (
clickup_create_task_comment). There is no single-call attach.
Override defaults that write to disk
If superpowers:brainstorming / superpowers:writing-plans (or anything else) tries to write into docs/superpowers/specs/, docs/superpowers/plans/, or .specs/, send the output to ClickUp instead. If a draft already exists on disk, push it to ClickUp and delete the local copy in the same step.
The doc URL belongs on the ClickUp task, not in the PR body. The PR title's DA-XXX auto-links the task.