frontdesk-intake

Solid

Convert user conversation into macro workflow requests and present curated clarification or final artifacts.

AI & Automation 3,329 stars 323 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 83/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Frontdesk Intake Use this skill for user-facing workflow intake and reporting. ## Inputs - user request - current macro decisions - broker question artifact - final or escalation artifact ## Outputs - macro task request for planner - concise user clarification display - final summary or escalation report Every turn, classify the user message before acting: - Direct answer or clarification: answer concisely and do not forward. - Macro task or workflow request: produce importable intake, submit it directly to Planner with the one allowed silent ask, and stop. - Blocked prerequisite: produce structured blocked evidence, submit it directly to Planner with the same allowed silent ask, and stop. - Final report or escalation: summarize evidence and do not forward. For a final report, consume only a validated Planner status envelope with schema `ccb.planner.frontdesk_status.v1`. Preserve `pass|partial|replan_required|blocked`, accepted scope, unresolved scope, blockers, structured next milestone, and evidence refs exactly. Render the Planner-authored `user_report_body`; do not reconstruct a report from child logs. Never claim global completion from decomposition or one successful child task. Do not forward this status back to Planner. The validated envelope remains byte-for-byte evidence. In final-report mode, render only `user_report_body`; never forward the status, call the Planner handoff capability, mutate authority, or add a second interpretation. If the schema or...

Details

Author
SeemSeam
Repository
SeemSeam/claude_codex_bridge
Created
9 months ago
Last Updated
today
Language
Python
License
NOASSERTION

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

intake-desk

The conversational front door for intake — turns a half-formed idea into a well-formed, correctly-typed, correctly-placed work item logged to the work tracker, never a scratch file. Meets you at any altitude (a single bug or a portfolio initiative), proposes the work-item type and its place in the intake hierarchy, elicits the type- and level-appropriate fields (a bug's reproduction and environment; a story's acceptance criteria and value), applies the 5-test rule live, and confirms before logging. One work item per request (child candidates noted in the body for later slicing; no auto-decompose). Two interactive modes — Elicit (guided interview) and Triage-readiness check (5-test a draft you wrote) — plus Ambient Auto-Log (Mode C), a non- interactive path invoked programmatically, not by a conversational phrase. Use when the user says "help me file this idea as an issue", "turn this into a work item", "log this idea", "is this intake-ready", or "help me write up this bug/story/initiative".

0 Updated today
cody-hutson
Code & Development Listed

intake

Manually triggered via /intake-toolkit:intake — the front door to the elicitation surface. Give it anything (a GitHub issue number, a pasted blob, a rough idea, an existing plan, a design handoff) and it classifies the scenario and routes to the right skill. Dispatch-only; contains no elicitation protocol of its own. Do not auto-select this skill; the routed skills carry their own triggers.

1 Updated yesterday
manoldonev
AI & Automation Solid

planner-task-packet

Draft CCB workflow task packets, readiness recommendations, and candidate clarification questions without mutating authoritative state.

3,329 Updated today
SeemSeam