epic-evaluation-axis-estimator

Analyze GitHub Epic text and related messages to infer hidden decision criteria and trade-offs for planning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kentoku24/project-guild --skill epic-evaluation-axis-estimator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-evaluation-axis-estimator
Source: https://github.com/kentoku24/project-guild/tree/main/docs/skills/epic-evaluation-axis-estimator
Command: npx skills add https://github.com/kentoku24/project-guild --skill epic-evaluation-axis-estimator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes GitHub Epics and related contributor-manager conversations to reveal the hidden decision criteria, dominant trade-offs, and risk sensitivities guiding those Epics.

Core Features & Use Cases

  • Infer implicit decision criteria from Epic descriptions and discussion threads to guide prioritization and planning.
  • Identify dominant trade-off axes (cost, risk, speed, impact) and likely pushback points to prepare stakeholders.
  • Translate qualitative dialogue into concrete evaluation signals that feed risk assessments and decision frameworks.

Quick Start

Paste the GitHub Epic text and related conversation logs to begin inferring the manager's hidden decision criteria.

Frequently Asked Questions about epic-evaluation-axis-estimator

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

FAQPage Schema
How do I infer hidden decision criteria from GitHub Epics and conversations?

To infer hidden decision criteria from Epics, analyze the Epic text and related discussion threads to reveal priorities, risks, and trade-offs guiding the project. This translates qualitative dialogue into concrete evaluation signals.

What is Epic trade-off analysis and how does it work?

Epic trade-off analysis identifies dominant trade-off axes like cost, risk, speed, and impact from project descriptions. It processes qualitative dialogue to generate a prioritized axis and concrete evaluation items for planning.

How do I identify risk sensitivities and pushback points for Epic planning?

Identify risk sensitivities and likely pushback points by analyzing manager-contributor conversations related to the Epic. This reveals hidden decision criteria and prepares stakeholders for potential challenges during prioritization.

Can I use conversation logs to extract evaluation signals for software projects?

Yes, you can paste GitHub Epic text and related conversation logs to extract concrete evaluation signals. The analysis translates qualitative dialogue into prioritized axes and evaluation items for risk assessments.

What's the best way to analyze Epic descriptions for prioritization and planning?

The best way to analyze Epic descriptions for prioritization is inferring implicit decision criteria from text and discussions. This reveals dominant trade-offs and potential pushback points to guide software project planning.