skills.rest
jstoup111
jstoup111COMMUNITY
Explore all skills by this author →
GitHub

intake

Create GitHub intake issues with evidence, impact, and desired outcomes.

5|1|Updated Mar 30, 2026
Search Tags:#GitHub#issue management#bug reporting#intake issue#enhancement ideas
One-click install
npx skills add https://github.com/jstoup111/ai-conductor --skill intake-jstoup111
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: intake
Source: https://github.com/jstoup111/ai-conductor/tree/main/skills/intake
Command: npx skills add https://github.com/jstoup111/ai-conductor --skill intake-jstoup111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps operators and agents create well-structured GitHub intake issues that clearly define problems, outcomes, and avoid prescribing solutions.

Core Features & Use Cases

  • Structured Issue Creation: Guides users through creating intake issues with clear evidence, impact, and desired outcomes.
  • Avoids Solution-Driven Issues: Ensures issues are focused on what needs to be fixed rather than how it should be done.
  • Use Case: When filing a bug report or an enhancement idea, use this Skill to structure the issue so it's clear and actionable for the DECIDE phase.

Quick Start

Run the 'intake' skill to create a new intake issue in GitHub with the following details: observed evidence, impact, desired outcome, and hypotheses.

Frequently Asked Questions about intake

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

FAQPage Schema
How do I write a structured GitHub intake issue for bug reporting?▼

To create a structured GitHub intake issue, you need to document observed evidence, impact analysis, and desired outcomes. This approach ensures bug reporting focuses on the problem rather than prescribing specific solutions.

What should a GitHub enhancement request include to be actionable?▼

A GitHub enhancement request should include observed evidence, impact analysis, and desired outcomes without specifying solutions. This structure provides clear, actionable context for downstream DECIDE phase analysis in software development workflows.

Why avoid solution-driven GitHub issues during intake?▼

Avoiding solution-driven GitHub issues ensures the intake process captures the problem scope accurately through evidence and impact. Prescribing solutions prematurely restricts analysis during the DECIDE phase and limits potential enhancement ideas.

How do I automate intake issue creation for GitHub?▼

You can automate intake issue creation for GitHub by running the 'intake' skill, which guides users through generating structured content including observed evidence, impact, desired outcomes, and hypotheses.

Does issue management workflow require specific structure for the DECIDE phase?▼

Yes, the DECIDE phase requires a proper issue structure that includes observed evidence, impact analysis, and desired outcomes. Structured intake issues provide the necessary foundation for this analysis without prescribing solutions.

Related Skills

Explore More Software Engineering Skills→
ajstack22ajstack22

atlas-agent-peer-reviewer

Review pull requests and patches with evidence-based verdicts.

Community
Intermediate
deanpetersdeanpeters
6.4k

recommendation-canvas

Generates a structured AI recommendation canvas with problem framing, hypotheses, risks, and next steps.

Community
Advanced
ToqsickToqsick

github-grayhack-workflow

Automate GitHub issue creation, branch management, pull requests, and documentation updates.

Community
Advanced
thydethyde

github-issues

Create, update, and search GitHub issues with LucidData templates and labels.

Community
Intermediate