agentdev-intake-pipeline

Extracts remaining issues from closed GitHub Issues and PRs, then reviews and promotes intake items.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-intake-pipeline-yogata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentdev-intake-pipeline
Source: https://github.com/yogata/agent-dev-flow/tree/main/src/opencode/skills/agentdev-intake-pipeline
Command: npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-intake-pipeline-yogata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Closed GitHub Issues and PRs often contain unchecked checkboxes, deferred tasks, and implicit follow-ups that get lost. This Skill provides the knowledge base for extracting those remaining issues into structured intake items and then reviewing, classifying, and routing them into a promoted backlog pipeline. ## Core Features & Use Cases - GitHub Residual Issue Extraction: Interprets natural-language date ranges, fetches closed Issues/PRs via gh CLI, detects unchecked checkboxes structurally, and runs LLM full-text analysis for implicit remaining tasks (TODO, deferred items, future concerns). - Intake Review and Classification: Reviews inbox items for validity, impact, urgency, and relation to existing requirements, then classifies them as adopt, hold, or reject with user confirmation before any persistence. - Promotion and Git Persistence: Formats adopted items into .agentdev/intake/promoted/, deletes rejected items with audit-trailed commit messages, and performs safe git pull/add/commit/push with structured error handling. - Use Case: After closing a sprint's worth of Issues, run the intake pipeline to collect every unchecked checkbox and deferred note, review the findings with the user, and promote approved items for downstream backlog review. ## Quick Start Ask the agent to extract remaining issues from GitHub Issues and PRs closed in the last two weeks and review the resulting inbox items for promotion.

Frequently Asked Questions about agentdev-intake-pipeline

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

FAQPage Schema
How do I extract remaining tasks from closed GitHub Issues?▼

Use the intake-from-github flow, which fetches closed Issues and PRs via gh CLI within a date range, detects unchecked checkboxes structurally, and runs LLM full-text analysis for implicit remaining tasks. Each candidate becomes one intake item file in .agentdev/intake/inbox/.

How does intake-promote classify inbox items?▼

Intake-promote reviews each item for validity, impact, urgency, and relation to existing requirements, then presents a classification table of adopt, hold, or reject. Nothing is saved or moved until the user explicitly approves the classification.

Does the extraction include tracking Issues?▼

No. Issues labeled with role: tracking are excluded from extraction because closed tracking Issues indicate confirmed reflection, which conflicts with the goal of collecting unrecovered change candidates.

What happens to rejected intake items?▼

Rejected items are deleted immediately rather than archived, and the rejection reason is included in the git commit message to strengthen the audit trail. Adopted items move to .agentdev/intake/promoted/ and held items stay in the inbox.

When should an item go to learning instead of intake?▼

When an item has no concrete fix target and only contains recurrence-prevention knowledge, it is routed to the learning pipeline instead of intake. The boundary judgment is defined in the workflow orchestration knowledge base.