dex-plan

Convert markdown planning documents into dex tasks with optional subtasks.

9|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/eliaskc/kajji --skill dex-plan-eliaskc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dex-plan
Source: https://github.com/eliaskc/kajji/tree/main/.agents/skills/dex-plan
Command: npx skills add https://github.com/eliaskc/kajji --skill dex-plan-eliaskc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting Markdown planning documents into trackable dex tasks to bridge planning and execution workflows.

Core Features & Use Cases

  • Converts planning, specifications, design documents, and roadmaps into a primary dex task with preserved context.
  • Analyzes plan structure to determine whether to automatically generate subtasks and how they are linked.
  • Provides a traceable context by keeping full markdown in the task description for future reference.

Quick Start

Run a planning-to-task workflow by providing a planning markdown file to the dex-plan command and let it generate the parent task and optional subtasks as appropriate.

Frequently Asked Questions about dex-plan

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

FAQPage Schema
How do I convert a markdown planning document into trackable tasks?

To convert markdown planning documents into trackable tasks, the workflow parses headings and content to generate a primary task, preserving full context in the description and automatically generating optional subtasks when the structure warrants.

Can I automatically generate subtasks from markdown headings and content?

Yes, you can automatically generate subtasks from markdown headings. The workflow analyzes the plan structure to determine whether to automatically generate subtasks and establishes how they are linked to the parent task.

Does the task conversion preserve the original markdown planning context?

Yes, task conversion preserves the original markdown planning context. The full markdown content is kept in the task description, providing a traceable reference for future execution workflows.

What is the best way to turn design specifications and roadmaps into a parent task?

The best way to turn design specifications and roadmaps into a parent task is using a planning-to-task workflow that analyzes the document structure to create a main task with optional subtasks while retaining full context.

How do I start a planning-to-task workflow for a markdown file?

To start a planning-to-task workflow, provide a planning markdown file to the workflow command. It will analyze the document structure and generate the parent task along with any appropriate subtasks automatically.