One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-ai-integration-phase-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-ai-integration-phase
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-ai-integration-phase
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-ai-integration-phase-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI integration phases often lack a concrete contract guiding framework selection, documentation guidance, and evaluation strategy, leading to misalignment and scope creep across AI projects.

Core Features & Use Cases

  • Orchestrates gsd-framework-selector → gsd-ai-researcher → gsd-domain-researcher → gsd-eval-planner to author a cohesive AI-SPEC.md.
  • Provides framework selection guidance, distilled from official docs, and a clear evaluation strategy for AI projects.
  • Generates AI-SPEC.md as a contract artifact to anchor phase deliverables and acceptance criteria.

Quick Start

Generate an AI-SPEC.md contract for the current AI integration phase.

Frequently Asked Questions about gsd-ai-integration-phase

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

FAQPage Schema
How do I define an AI design contract for an AI integration phase?

To define an AI design contract, generate an AI-SPEC.md artifact covering framework selection, documentation guidance, and evaluation strategy. This artifact specifies deterministic execution flow and acceptance criteria to anchor AI system deliverables.

How do I create an evaluation strategy for AI system development?

Create an evaluation strategy by orchestrating workflow steps that produce an AI-SPEC.md artifact. This process integrates evaluation planning to establish clear metrics and acceptance criteria for your AI integration phase.

What is the best way to align AI framework selection with project documentation?

Align framework selection with documentation by distilling implementation guidance from official docs into an AI-SPEC.md contract. This approach prevents misalignment and scope creep across AI integration projects.

Does this workflow orchestration tool require external dependencies to run?

This workflow orchestration requires no external dependencies to generate an AI-SPEC.md. It coordinates internal workflow steps like framework selection and evaluation planning natively to produce the complete contract artifact.

Why does my AI integration phase suffer from scope creep?

AI integration phases suffer from scope creep due to a lack of a concrete contract guiding framework selection and evaluation strategy. Generating an AI-SPEC.md artifact anchors deliverables and prevents this misalignment.