Normalize raw work requests into structured intake_output JSON artifacts.
npx skills add https://github.com/anderson-joyle/claude-a-team --skill skill-intake
Please help me install this Agent Skill. Skill: Skill: Intake Source: https://github.com/anderson-joyle/claude-a-team/tree/main/skills/intake Command: npx skills add https://github.com/anderson-joyle/claude-a-team --skill skill-intake
It prevents downstream misunderstandings by turning raw, inconsistent work requests into a structured, evidence-aware intake artifact that the rest of the workflow can trust.
Use the /intake skill to normalize a new engineering work request by providing its raw demand and the runtime request envelope so it can emit a single intake_output JSON artifact.
High-intent search queries and answers about installing and using this skill.
To normalize raw work requests, you apply an intake process that converts inconsistent demand and runtime envelope inputs into a typed JSON artifact with derived titles, preserving evidence paths and tracking references for reliable downstream processing.
Request normalization is the process of structuring raw demand into a consistent internal representation. It is needed to prevent downstream misunderstandings by ensuring every engineering or architectural decision relies on a consistent, evidence-aware intake artifact.
Evidence preservation works by keeping original request constraints, evidence paths, and tracking references intact within the emitted JSON artifact. This ensures auditable, stage-by-stage processing as the workflow progresses through subsequent routing gates.
Yes, the normalized intake artifact provides routing suggestions that recommend which later gates, such as Architect, Security, Review, or Release Readiness, should execute next based on what the specific engineering request requires.
Yes, you need to provide the raw demand along with the runtime request envelope. The intake process uses both to emit a single structured intake_output JSON artifact and asks only blocking questions required for accurate classification.
anderson-joyleGenerate architecture guidance for contract, schema, and runtime-impacting changes.
Me1eConvert natural-language wizard requests and RunSpec into typed intent contracts.
marcusrbrownGuide discovery, exploration, and design capture before planning.
giadaf-booshaCategorize customer support tickets, assign priorities, and recommend routing.
