evaluate-story

Evaluate software story complexity and assign delivery tiers.

157|28|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Fr-e-d/GAAI-framework --skill evaluate-story-fr-e-d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluate-story
Source: https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/delivery/evaluate-story
Command: npx skills add https://github.com/Fr-e-d/GAAI-framework --skill evaluate-story-fr-e-d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the initial assessment of a software development story, determining its complexity, required specialist domains, and appropriate delivery tier, ensuring efficient resource allocation and risk management before delivery begins.

Core Features & Use Cases

  • Complexity Assessment: Analyzes story fields, acceptance criteria, and file impact to gauge difficulty.
  • Domain Identification: Scans story details for keywords to identify necessary specialist expertise.
  • Skill Coverage Verification: Checks if existing skills in the index can support the identified domains.
  • Tier Determination: Assigns a delivery tier (MicroDelivery, Core Team, Core Team + Specialists).
  • Risk Analysis Triggering: Identifies stories requiring pre-flight risk assessment.
  • Use Case: Before a new feature is handed off for development, this skill is run to classify it, flag any potential skill gaps, and decide if it needs a specialized team or can be handled by the core development group.

Quick Start

Run the evaluate-story skill on the attached story artefact to determine its delivery tier and identify any required specialists.

Frequently Asked Questions about evaluate-story

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

FAQPage Schema
How do I assess story complexity and determine the delivery tier for software development?

To assess story complexity and determine the delivery tier, evaluate story artefacts, acceptance criteria, and file impact. This process assigns a delivery tier of MicroDelivery, Core Team, or Core Team + Specialists based on detected complexity signals.

What is domain identification in story evaluation and when do I need specialist engagement?

Domain identification in story evaluation scans story details for keywords to identify necessary specialist expertise. You need specialist engagement when domain triggers indicate required skills exceed the core team's coverage.

How do I perform a skill gap analysis before handing off a feature for development?

Perform a skill gap analysis by checking existing skills in the index against identified specialist domains. This verifies skill coverage and flags missing expertise required to support the story's delivery tier.

Can I use automated risk assessment to trigger pre-flight checks for complex stories?

Yes, you can use automated risk assessment to trigger pre-flight checks for complex stories. The evaluation identifies stories requiring pre-flight risk analysis based on complexity signals and domain triggers.

What is the best way to classify a software story for resource allocation?

The best way to classify a software story for resource allocation is to scan story artefacts and skill indexes to output the delivery tier, triggered specialists, and skill gaps, ensuring efficient team assignment before delivery begins.