intake

Automate issue, change, and incident capture into a standardized CR workflow.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/Angel1104/architecture-docs --skill intake-angel1104
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intake
Source: https://github.com/Angel1104/architecture-docs/tree/main/FE-MOBILE/commands/intake
Command: npx skills add https://github.com/Angel1104/architecture-docs --skill intake-angel1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Intake skill provides a universal entry point for reporting issues, change requests, or incidents and converts them into a standardized CR item, reducing gate time and ensuring consistent triage.

Core Features & Use Cases

  • Universal entry point for any input type (plain text, file, URL, Jira ticket, log, or findings report).
  • Classifies input, assesses risk and impact, and produces a CR item ready for the process.
  • Supports optional execution of deterministic tasks via scripts, reads references for deeper context, and attaches assets for documentation.

Quick Start

Describe the issue or input you want triaged to initiate the intake flow.

Frequently Asked Questions about intake

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

FAQPage Schema
How do I automate triage for incoming issues and change requests?

Automating triage for incoming issues requires a unified intake workflow that captures inputs from plain text, files, URLs, Jira tickets, or logs and classifies them into a standardized CR item. This ensures consistent risk assessment across the development lifecycle.

What is the best way to standardize incident reports into a CR workflow?

Standardizing incident reports into a CR workflow involves routing any input type through a consistent classification and risk assessment flow. This captures the findings and converts them into a standardized change request item ready for processing.

Can I process Jira tickets and raw logs through the same intake routing?

Yes, you can process Jira tickets and raw logs through the same intake routing. The workflow handles inputs from plain text, files, URLs, tickets, or logs and applies a consistent triage flow to produce a standardized CR item.

How do I start the triage flow for an unstructured issue report?

To start the triage flow for an unstructured issue report, simply describe the issue or input you want triaged. The intake process automatically captures the text, classifies it, and assesses its risk and impact to generate a CR item.

Does the intake workflow support executing deterministic tasks via scripts?

Yes, the intake workflow supports executing deterministic tasks via scripts. It reads references for deeper context and attaches assets for documentation, using optional scripts to support downstream steps in the development lifecycle.

What distinguishes a unified intake workflow from manual issue triage?

A unified intake workflow distinguishes itself from manual triage by providing a universal entry point for any input format. It reduces gate time by automating risk assessment and ensuring consistent classification into standardized CR items across the lifecycle.