planning

Convert PRDs and briefs into structured epics, stories, and tasks.

8|2|Updated Jan 15, 2026

Search Tags:#planning #epics #PRD #tasks #kanban #stories #project-management

Ready to run

npx skills add https://github.com/srstomp/pokayokay --skill planning-srstomp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/srstomp/pokayokay/tree/main/plugins/pokayokay/skills/planning
Command: npx skills add https://github.com/srstomp/pokayokay --skill planning-srstomp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

An automated workflow that converts PRDs, concept briefs, and feature specifications into a structured plan consisting of epics, stories, and tasks with clear dependencies and estimates, reducing manual planning time and ensuring a consistent project context.

Core Features & Use Cases

Break requirements into epic → story → task hierarchies with dependencies and time estimates.
Generate planning artifacts such as PROJECT.md, tasks.db, features.json, and kanban.html for Kanban tracking and cross-skill routing.
Flag ambiguities in requirements and assign primary skills to features to guide automated routing.

Quick Start

Run the plan command with your PRD path to generate all planning artifacts and populate the shared context for downstream skills.

Frequently Asked Questions about planning

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

FAQPage Schema

How do I turn a PRD into actionable epics, stories, and tasks?▼

To turn a PRD into epics, stories, and tasks, you can automatically analyze PRD-like documents to produce a hierarchical breakdown with dependencies and estimates. This reduces manual planning time and ensures consistent project context for kanban tracking.

What is the best way to generate a kanban board from a product brief?▼

Generating a kanban board from a product brief is best done by automating the extraction of features into a hierarchical plan. This process outputs a kanban.html file along with PROJECT.md, tasks.db, and features.json to enable multi-skill orchestration and tracking.

How do I break down project requirements with dependencies and time estimates?▼

You can break down project requirements with dependencies and time estimates by analyzing concept briefs and feature specifications. The workflow maps out an epic to story to task hierarchy, flagging ambiguities and assigning primary skills to guide automated routing.

Can I use a PRD to populate a tasks database for project management?▼

Yes, you can use a PRD to populate a tasks database for project management. Analyzing the PRD automatically generates a tasks.db file along with other planning artifacts, establishing a shared context for downstream skills and kanban tracking.

Does automated PRD planning flag ambiguities in feature specifications?▼

Automated PRD planning does flag ambiguities in feature specifications. During the breakdown into epics, stories, and tasks, the workflow identifies unclear requirements and assigns primary skills to features to guide automated routing and resolve context gaps.