plan-to-clickup

Parse CE plan YAML frontmatter into epics and subtasks.

Updated May 21, 2025
One-click install
npx skills add https://github.com/jonparkdev/nix-config --skill plan-to-clickup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-to-clickup
Source: https://github.com/jonparkdev/nix-config/tree/main/ai/skills/plan-to-clickup
Command: npx skills add https://github.com/jonparkdev/nix-config --skill plan-to-clickup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CE planning often yields high-level plans that miss hidden work. This skill decomposes a Compound Engineering (CE) plan into sprint-scoped ClickUp epics and subtasks, surfacing overlooked work for reliable execution.

Core Features & Use Cases

  • Four-lens decomposition: Prerequisite/Core/Verify, Implicit Dependencies, Glue Work, and Definition of Done to surface gaps.
  • Epic-to-subtask scoping: Generates a single epic with a structured set of subtasks per plan section.
  • Intermediate document generation: Writes docs/plans/<original-name>-decomposed.md with traceability back to the source plan.
  • ClickUp integration (optional): Creates tasks and subtasks via MCP when a list is provided.

Quick Start

Provide a path to a CE plan file and a ClickUp list ID to decompose the plan into sprint-ready epics and tasks.

Frequently Asked Questions about plan-to-clickup

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

FAQPage Schema
How do I decompose a high-level engineering plan into sprint-ready tasks?▼

You decompose an engineering plan by parsing its YAML frontmatter, identifying top-level sections as epics, and applying a four-lens decomposition to surface hidden work and map it to structured subtasks for sprint planning.

What is the four-lens decomposition method for sprint planning?▼

The four-lens decomposition method for sprint planning analyzes plans through Prerequisite/Core/Verify, Implicit Dependencies, Glue Work, and Definition of Done lenses to surface overlooked work and generate comprehensive epics and subtasks.

Can I sync decomposed epics and subtasks directly to ClickUp?▼

Yes, you can sync decomposed epics and subtasks directly to ClickUp via MCP when a ClickUp list ID is provided, automatically creating structured tasks and subtasks from the decomposed plan sections.

Do I need a specific file format to decompose CE plans into epics?▼

Yes, you need a CE plan document with YAML frontmatter for decomposing into epics and subtasks. The skill parses the frontmatter and identifies top-level sections to generate sprint-ready work items.

What's the best way to surface hidden dependencies in sprint planning?▼

The best way to surface hidden dependencies in sprint planning is applying a decomposition lens specifically targeting Implicit Dependencies, alongside Glue Work and Definition of Done lenses, to reveal overlooked work before execution.

Does decomposing plans into ClickUp tasks generate traceable documentation?▼

Yes, decomposing plans generates an intermediate markdown document at docs/plans/<original-name>-decomposed.md that contains the decomposed epics and subtasks with full traceability back to the source CE plan.