planner

Coordinate planning tasks and knowledge management in a PKB into actionable epics.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nicsuzor/aops --skill planner-nicsuzor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/nicsuzor/aops/tree/main/aops-claude/skills/planner
Command: npx skills add https://github.com/nicsuzor/aops --skill planner-nicsuzor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates planning tasks and PKM governance within a knowledge base to structure fragments into actionable epics, improving clarity and traceability.

Core Features & Use Cases

  • Modes: capture, plan, decompose, explore, and maintain to cover the full planning lifecycle.
  • Graph ownership: you manage the graph of tasks, epics, and projects, surfacing dependencies and constraints.
  • Knowledge health: prune, reparent, and densify the PKB to keep the knowledge graph consistent.
  • Use Case: Decompose a strategic epic into a concrete task tree and surface the next steps for execution.

Quick Start

Provide an initial plan to decompose the current epic into actionable tasks and surface the next steps.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I decompose strategic epics into actionable task trees?

Epic decomposition breaks down strategic fragments into a concrete task tree by applying planning workflows within a PKB. This surfaces task dependencies and next steps to improve clarity and traceability for execution.

What is knowledge management governance in a personal knowledge base?

Knowledge management governance in a PKB involves pruning, reparenting, and densifying the knowledge graph to maintain consistency. It applies hierarchical governance and frontmatter-driven metadata to ensure traceable planning across projects.

How do I capture and plan tasks using a task graph workflow?

You capture and plan tasks using a task graph workflow by operating across capture, plan, decompose, explore, and maintain modes. This manages the graph of tasks, epics, and projects to surface dependencies and constraints across the planning lifecycle.

Does this planning approach support task dependencies and hierarchical metadata?

Yes, this planning approach supports task dependencies and hierarchical governance by applying frontmatter-driven metadata within a personal knowledge base. This ensures traceable planning and surfaces constraints across task graphs and project epics.

What is the best way to maintain knowledge health in a task graph?

The best way to maintain knowledge health in a task graph is to use maintenance modes that prune, reparent, and densify the PKB. This keeps the knowledge graph consistent and optimizes planning tasks across the full lifecycle.

When should I not use a PKB planning workflow for project management?

You should avoid a PKB planning workflow when your project lacks frontmatter-driven metadata or hierarchical governance requirements. It is designed for structuring fragments into actionable epics with traceable dependencies, not for simple unstructured task lists.