plan-w-team

Decompose requests into GitHub Issues with labels, dependencies, and acceptance criteria.

Updated Aug 27, 2026

Search Tags:#planning #collaboration #github #epics #issues #project-management

Ready to run

npx skills add https://github.com/declanshanaghy/fenrir-ledger --skill plan-w-team

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-w-team
Source: https://github.com/declanshanaghy/fenrir-ledger/tree/main/.claude/skills/plan-w-team
Command: npx skills add https://github.com/declanshanaghy/fenrir-ledger --skill plan-w-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break work into GitHub Issues with labels, dependencies, and acceptance criteria. Interviews Odin via Freya, wireframes via Luna (if UI), then files issues to the Project board and writes an epic dependency graph to tmp/epics/<N>.yml for /epic-manager to track. Use when the user says 'plan', 'plan with team', 'break this into issues', or describes a feature/bug needing structured planning.

Core Features & Use Cases

Interviews Odin via Freya to clarify requirements and acceptance criteria.
Breaks work into GitHub Issues with labels, dependencies, and acceptance criteria.
If UI is involved, coordinates Luna for wireframes; files issues to the Project board.
Writes an epic dependency graph to tmp/epics/<N>.yml for the epic-manager to track.

Quick Start

Provide a user prompt describing the objective and plan-w-team will generate linked GitHub Issues and an epic graph for tracking.

Frequently Asked Questions about plan-w-team

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

FAQPage Schema

How do I break a feature request into GitHub Issues with dependencies and acceptance criteria?▼

To break a feature request into GitHub Issues with dependencies and acceptance criteria, provide a high-level prompt describing your objective. The system decomposes the request, conducts an interview to clarify requirements, and files linked issues to the GitHub Project board.

How does multi-agent GitHub planning handle UI wireframing during issue decomposition?▼

Multi-agent GitHub planning handles UI wireframing by coordinating a dedicated UI agent when interface design is needed. It generates wireframes alongside the structured issues, ensuring visual requirements are captured before filing the issues to the project board.

What is an epic dependency graph and how is it generated for GitHub project management?▼

An epic dependency graph is a structured representation of issue relationships written to a YAML file. It is generated after decomposing high-level requests into GitHub Issues, mapping the dependencies between epics to enable continuous tracking by an epic manager.

Do I need a GitHub Project board to break down work into structured issues?▼

Yes, a GitHub Project board is required to file the decomposed issues. The planning process creates GitHub Issues with labels, dependencies, and acceptance criteria, then files these issues directly to the project board for tracking.

Can I use structured planning for bugs that need labels and acceptance criteria?▼

Yes, you can use structured planning for bugs by describing the bug. The process decomposes the bug into GitHub Issues with appropriate labels, dependencies, and acceptance criteria, then files them to the project board and generates an epic dependency graph.

What are the limitations of automated GitHub issue decomposition for complex projects?▼

Automated GitHub issue decomposition relies on an interview process to clarify requirements, meaning incomplete or vague initial prompts may result in less accurate issues. It also requires manual epic tracking using the generated dependency graph file.