Verified:GitHub

story-intake

Fetch and normalize work items from ADO, Jira, GitLab, GitHub, Zoho, or markdown.

11|4|Updated Apr 27, 2026

Search Tags:#story #issue #acceptance-criteria #work-item #clarifying-questions #intake #provider-adapter

One-click install

npx skills add https://github.com/MostAshraf/ai-sdlc-harness --skill story-intake-mostashraf

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: story-intake
Source: https://github.com/MostAshraf/ai-sdlc-harness/tree/main/skills/story-intake
Command: npx skills add https://github.com/MostAshraf/ai-sdlc-harness --skill story-intake-mostashraf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull and analyse a User Story / Issue from the configured work item provider. Use when starting Phase 1 of the development workflow — ingesting requirements, parsing acceptance criteria, and surfacing clarifying questions before planning begins. Supports ADO, Jira, GitLab, GitHub, Zoho, and local-markdown via provider adapters.

Core Features & Use Cases

Provider-agnostic fetch and parse of work items from ADO, Jira, GitLab, GitHub, Zoho, and local-markdown.
Normalizes Title, Description, Acceptance Criteria, Status, Area/Labels, Iteration, Linked Items, and Attachments into a consistent schema.
Generates clarifying questions to surface gaps before planning.

Quick Start

Provide a Work Item ID to fetch from the active provider and receive a structured intake with clarifying questions.

Frequently Asked Questions about story-intake

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

FAQPage Schema

How do I ingest user stories from Jira and ADO for development planning?▼

Story intake ingests user stories from Jira, ADO, GitLab, GitHub, Zoho, and local markdown by fetching work items via provider adapters. It normalizes title, description, and acceptance criteria into structured markdown, generating clarifying questions to surface requirement gaps before planning begins.

What is the best way to parse acceptance criteria from work items across multiple providers?▼

Parsing acceptance criteria across multiple providers uses a provider-agnostic adapter framework that resolves configurations and fetches items from sources like ADO, Jira, and GitLab. It normalizes extracted criteria, status, and linked items into a consistent schema for downstream automation.

Can I fetch work items from local markdown files instead of a provider like Jira?▼

Yes, local markdown is supported as a provider alongside ADO, Jira, GitLab, GitHub, and Zoho. The provider resolution mechanism processes local markdown sources, normalizing title, description, and acceptance criteria into structured fields identical to remote provider output.

Do I need to configure provider settings before fetching issues from Azure DevOps?▼

Provider configuration is required before fetching issues from Azure DevOps or other providers. The intake process resolves settings via a provider-config file, enabling adapters to authenticate, fetch work items, and normalize data into markdown with structured fields and clarifying questions.

How do I generate clarifying questions for requirements gathered from GitHub issues?▼

Generating clarifying questions for GitHub issues happens automatically during intake after the adapter fetches and parses the work item. The process analyzes the normalized title, description, and acceptance criteria to surface requirement gaps before development planning begins.

What structured data fields are extracted when ingesting work items for automation workflows?▼

Ingesting work items extracts title, description, acceptance criteria, status, area or labels, iteration, linked items, and attachments. These fields are normalized into a consistent markdown schema, enabling structured downstream automation and clarifying question generation.