skills.rest
jfriisj
jfriisjCOMMUNITY
Explore all skills by this author →
GitHub

planka-workflow

Synchronize roadmap Epics to Planka with Markdown and MCP tools.

Updated Mar 20, 2026
Search Tags:#workflow#mcp#epics#agile#kanban#project-management#planka
One-click install
npx skills add https://github.com/jfriisj/coding-agents --skill planka-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planka-workflow
Source: https://github.com/jfriisj/coding-agents/tree/main/.github/skills/planka-workflow
Command: npx skills add https://github.com/jfriisj/coding-agents --skill planka-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Agile teams often struggle to keep Epics synchronized across the project roadmap, the Obsidian memory graph, and the live Planka board. This skill enforces a single source of truth in Markdown while providing live visibility via Native MCP Tools and prohibits Python scripts.

Core Features & Use Cases

  • Synchronizes Epics from roadmap to Planka Epics board, creating a canonical Epic card structure with AC task-lists, labels, and status lists.
  • Decomposes Acceptance Criteria into AC1...ACN task-lists, enforces exact cardinality, reconciles legacy planner lists, and maintains an auditable handoff via comments.
  • Enforces governance using only Native MCP Tools, tracking time, status transitions, and ensuring compliant epics across cross-functional workstreams.

Quick Start

Prepare the Markdown artifact and synchronize the Planka Epic with AC task-lists using only Native MCP Tools.

Frequently Asked Questions about planka-workflow

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

FAQPage Schema
How do I synchronize project roadmap Epics to a Planka board?▼

To synchronize Epics to Planka, the skill applies a canonical Epic card structure with native MCP tools, mapping acceptance criteria to task-lists and enforcing lifecycle stages from Planned to Closed while maintaining a Markdown single source of truth.

What is the best way to track cross-functional Epic execution in Planka?▼

Tracking cross-functional Epic execution in Planka requires decomposing acceptance criteria into explicit AC1...ACN task-lists, enforcing cardinality, and applying status transitions across Planned, In Progress, Delivered, Deferred, and Closed stages via native MCP tools.

How does acceptance criteria to task mapping work for agile Epics?▼

Acceptance criteria to task mapping works by decomposing criteria into exact AC1...ACN task-lists within the Planka Epic card, enforcing precise cardinality, reconciling legacy planner lists, and ensuring an auditable handoff through comments and artifact links.

Can I use custom Python scripts for Planka project management with this workflow?▼

Custom Python scripts are prohibited for Planka project management in this workflow; governance and time tracking are enforced exclusively through native MCP tools to guarantee compliant epic transitions and auditable artifact links.

Why do my legacy planner lists need reconciliation during Epic synchronization?▼

Legacy planner lists need reconciliation during Epic synchronization to enforce exact AC-list cardinality, prevent forbidden names, and maintain a single source of truth between the Markdown roadmap and the live Planka board.

Does the Planka workflow support tracking deferred or closed Epic stages?▼

The Planka workflow supports tracking deferred and closed Epic stages by enforcing lifecycle transitions across Planned, In Progress, Delivered, Deferred, and Closed states while reconciling status lists with native MCP tools.

Related Skills

Explore More Product & Management Skills→
devmuslimdevmuslim

shared-roadmap

Generate a unified multi-team delivery roadmap with dependency visualization.

Community
Intermediate
majedsiefalnasrmajedsiefalnasr

stage-workflow-governance

Enforce stage lifecycle governance and block edits for CLOSED or HARDENED specs.

Community
Advanced
danielstewart77danielstewart77
1

story-start

Fetch a Planka card, create a project directory, and generate an implementation plan.

Community
Advanced
epieczkoepieczko

epic.decompose

Parse Markdown Epic documents and generate structured user stories as JSON.

Community
Intermediate