yak-mapping

Organize work by iteratively adding goals and blockers to surface actionable leaves.

3|3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/mrdavidlaing/yakthang --skill yak-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: yak-mapping
Source: https://github.com/mrdavidlaing/yakthang/tree/main/skills/yak-mapping
Command: npx skills add https://github.com/mrdavidlaing/yakthang --skill yak-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Traditional planning often freezes at upfront decomposition, leading to brittle schedules and misaligned teams. Yak-mapping enables emergent planning through action, letting work structure reveal itself as you proceed.

Core Features & Use Cases

  • Emergent planning via incremental yak addition and live mapping to surface blockers.
  • Leaf-first work discipline where tasks executable in a single session are identified and completed.
  • Context-driven briefs that define goals, done criteria, known unknowns to guide implementation.

Quick Start

Add a goal, then surface blockers by adding one child blocker under it and provide a concise context.

Frequently Asked Questions about yak-mapping

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

FAQPage Schema
What is emergent planning and how does it handle complex project blockers?

Emergent planning structures work by iteratively adding goals and surfacing blockers through action. It maps dependencies live, preventing upfront decomposition from freezing schedules and revealing the project structure as execution proceeds.

How do I map leaf tasks for a new feature without upfront decomposition?

Add a goal, then iteratively identify child blockers beneath it. This workflow surfaces single-session leaf tasks executable immediately, providing concise context briefs and explicit done criteria to guide implementation without rigid decomposition.

When should I use an emergent task-mapping workflow instead of traditional scheduling?

Use emergent task-mapping for strategic goals and complex projects where structure reveals itself through action. It prevents brittle schedules by enforcing leaf-first work discipline and live blocker mapping rather than freezing plans upfront.

What's the best way to surface action items and known unknowns during project planning?

The best way is applying context-driven briefs alongside emergent planning. Define goals, done criteria, and known unknowns, then iteratively map child blockers to surface actionable leaf tasks executable in a single session.

Does emergent planning work for large scale strategic goals with many unknowns?

Yes, emergent planning handles complex strategic goals by enforcing a disciplined workflow. It iteratively surfaces blockers and defines explicit context templates, guiding execution even when the full project structure is initially unknown.

Why does traditional upfront decomposition fail to manage blockers in real time?

Traditional upfront decomposition freezes schedules and misaligns teams by assuming a rigid structure. Emergent planning solves this by iteratively adding goals and mapping child blockers live, revealing actionable leaf tasks as work progresses.