frontdesk-intake

Convert user conversations into structured macro workflow intake artifacts for planner handoff.

3.5k|342|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/bfly123/claude_code_bridge --skill frontdesk-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontdesk-intake
Source: https://github.com/bfly123/claude_code_bridge/tree/main/docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_frontdesk/skills/frontdesk-intake
Command: npx skills add https://github.com/bfly123/claude_code_bridge --skill frontdesk-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes how user-facing agents turn raw conversation into importable workflow requests, preventing ad-hoc implementation, duplicated submissions, and unvalidated status reporting in a multi-agent CCB pipeline.

Core Features & Use Cases

  • Strict message classification: Every user turn is classified as a direct answer, macro task request, blocked prerequisite, or final report before any action is taken.
  • Structured intake artifacts: Produces exact **Intake Evidence** or **Blocked Evidence** markdown shapes with a unique CCB_REQ_ID, scope, required behavior, and constraints for the Planner.
  • Single controlled handoff: Submits evidence exactly once via the Codex ccb_frontdesk_ask_planner tool or the Claude silent ask command, then stops.
  • Validated final reporting: Renders only Planner-authored user_report_body from a validated ccb.planner.frontdesk_status.v1 envelope without reconstructing reports from child logs.
  • Use Case: A user asks the frontdesk agent to create a documentation file; the skill returns an Intake Evidence artifact naming the path, required content, and authority limits, then hands off to the Planner instead of creating the file.

Quick Start

Ask the frontdesk agent to handle a new project request and it will classify the message, emit a structured Intake Evidence artifact, and forward it to the Planner exactly once.

Frequently Asked Questions about frontdesk-intake

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

FAQPage Schema
How do I route user requests to a planner agent in a multi-agent workflow?

Classify each user message first, then emit a structured Intake Evidence artifact containing a request ID, scope, required behavior, and constraints. Submit it once through the designated planner handoff channel and stop without performing the work yourself.

What is the Intake Evidence format for frontdesk workflow intake?

It is a markdown block starting with the heading **Intake Evidence**, followed by CCB_REQ_ID, a one-sentence macro request, Scope, Required behavior, Constraints, and the next step and role lines. The same ID must appear in the handoff call.

How should blocked requests be reported instead of implemented?

Use the **Blocked Evidence** shape with the request ID, the requested validation, the specific blocker such as missing credentials or approval, a routing recommendation, and prohibited actions. Submit it to the planner exactly once rather than simulating the work.

Can the frontdesk agent create or edit project files directly?

No. The skill forbids creating, editing, testing, or verifying any project artifacts. Even tiny file requests must be converted into an Intake Evidence artifact describing the path and required content for the planner.

How are final planner status reports rendered to users?

Only a validated envelope with schema ccb.planner.frontdesk_status.v1 is consumed, and only its planner-authored user_report_body is rendered. If the schema or validation marker is missing, the skill reports a blocker instead of reconstructing a report.