intake

Route incoming work to S/M/L tracks using a formal complexity score.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/quantfiction/dotfiles --skill intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intake
Source: https://github.com/quantfiction/dotfiles/tree/main/claude/plugins/global-skills/skills/intake
Command: npx skills add https://github.com/quantfiction/dotfiles --skill intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route incoming work to the appropriate track (S/M/L) based on a formal complexity score.

Core Features & Use Cases

  • Deterministic routing decisions based on a published scoring rubric.
  • Auditable routing decisions stored in the intake output for governance.
  • Applicable to projects with a ROUGH.md plan to determine track and research needs.

Quick Start

Create a rough plan at docs/plans/<project>/ROUGH.md and run intake to generate docs/plans/<project>/INTAKE.md with routing decisions recorded.

Frequently Asked Questions about intake

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

FAQPage Schema
How do I route incoming work to different project tracks based on complexity?

Work routing based on complexity uses a published scoring rubric to assign incoming tasks to S, M, or L tracks. It evaluates your rough plan to generate an intake document recording the selected track and research requirements for auditability.

What is the best way to create an audit trail for work routing decisions?

An audit trail for work routing is created by generating an intake document that captures deterministic routing decisions. The intake output stores the selected track and related governance decisions based on a formal complexity score.

How do I set up my project to use deterministic work routing?

To set up deterministic work routing, create a rough plan file at docs/plans/<project>/ROUGH.md. Running the intake process on this file generates routing decisions and outputs them to docs/plans/<project>/INTAKE.md.

Does work routing require a rough plan to determine if research is needed?

Yes, work routing requires a rough plan at docs/plans/<project>/ROUGH.md to function. It operates on this document to evaluate complexity and determine whether research is required before outputting the intake document.

Why do I need a formal complexity score for project planning?

A formal complexity score ensures deterministic routing decisions for project planning. By applying a published scoring rubric, it consistently categorizes work into appropriate tracks and records whether research is required for governance.