request-intake

Create task skeletons under workflows/tasks/<task-id> using python3 scripts/workflow.py.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/alexization/git-ranker-workflow --skill request-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-intake
Source: https://github.com/alexization/git-ranker-workflow/tree/main/.codex/skills/request-intake
Command: npx skills add https://github.com/alexization/git-ranker-workflow --skill request-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates turning new requests into a single, actionable task by creating the task artifact at workflows/tasks/<task-id> and enabling a clean handoff.

Core Features & Use Cases

  • Consolidates incoming requests into a single task to prevent fragmentation.
  • Generates a standardized task skeleton under workflows/tasks/<task-id>/ with spec.md and task.json, and enforces draft- and approval-stage gating before handoff to later steps like socratic-spec-authoring.
  • Supports common intake scenarios such as requests with no existing task artifact and multi-team handoffs, providing predictable paths and artifacts.

Quick Start

Create a new task skeleton for a given <task-id> using the workflow.py-based script.

Frequently Asked Questions about request-intake

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

FAQPage Schema
How do I automate turning new requests into executable tasks?

Automating new request conversion creates a single task artifact at workflows/tasks/<task-id>/ using a deterministic python3 workflow script, generating standardized task skeletons with spec.md and task.json for clean handoff.

What is the best way to consolidate incoming requests and prevent task fragmentation?

Consolidating incoming requests requires creating a single, actionable task artifact under workflows/tasks/<task-id>/ to prevent fragmentation, enforcing draft and approval stage gating before any handoff to downstream stages.

Can I use this request intake workflow for multi-team handoffs?

Yes, request intake workflows support multi-team handoffs by generating predictable task paths and standardized artifacts, ensuring the receiving team gets a structured task skeleton with spec.md and gated approvals.

How does draft and approval stage gating work for new task artifacts?

Draft and approval stage gating enforces stage transitions before handoff by requiring the creation of spec.md and task.json, ensuring the task skeleton passes through draft spec creation before moving to socratic-spec-authoring.

Do I need python3 to generate task skeletons from incoming requests?

Yes, deterministic task generation requires running python3 scripts/workflow.py with parameters like new <task-id> --title and --primary-repo to create the standardized task skeleton and enable stage transitions.