COS Request Intake

Parses Chief of Staff requests and generates staffing plans with specialist assignments.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sparkst/sparkry-claude-skills --skill cos-request-intake-sparkst
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: COS Request Intake
Source: https://github.com/sparkst/sparkry-claude-skills/tree/main/plugins/strategy-workflow/skills/cos/intake
Command: npx skills add https://github.com/sparkst/sparkry-claude-skills --skill cos-request-intake-sparkst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Strategic and product requests arrive ambiguous and unstructured, making it hard to decide what deliverable to produce, which specialists to involve, and how long the work will take. This Skill standardizes the triage of Chief of Staff requests into a repeatable intake process. ## Core Features & Use Cases - Deliverable Classification: Maps request patterns to deliverable types including requirements documents, PR-FAQs, buy-vs-build analyses, PMF validation plans, tenets, ADRs, and security reviews. - Specialist Staffing Plans: Identifies required roles (pm, ux-designer, pe-designer, sde-iii, legal-expert, finance-consultant, strategic-advisor) and outputs a structured cos/plan.json with tasks, effort estimates, and milestones. - Scope Clarification: Prompts targeted clarifying questions when requests are ambiguous before committing resources. - Use Case: A user asks to spec out a Slack integration. The Skill classifies it as a requirements deliverable, assigns pm, ux-designer, pe-designer, and sde-iii, estimates 5 story points over 3 days, and writes the staffing plan to cos/plan.json. ## Quick Start Ask the assistant to intake a new COS request such as creating requirements for a Slack integration feature and confirm the generated staffing plan.

Frequently Asked Questions about COS Request Intake

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

FAQPage Schema
How do I triage a Chief of Staff request into a deliverable plan?▼

Submit the raw request at the start of any COS engagement. The intake process classifies it into a deliverable type such as requirements, PR-FAQ, or buy-vs-build, then generates a staffing plan in cos/plan.json with assigned specialists, effort estimates, and milestones.

What deliverable types does COS request intake support?▼

It supports seven deliverable types: requirements documents, PR-FAQs, buy-vs-build analyses, PMF validation plans, tenets documents, architecture decision records, and third-party skill security reviews. Pattern matching on request keywords determines the classification, defaulting to requirements.

How are specialists selected for a COS staffing plan?▼

A selection matrix maps each deliverable type to always-required, often-required, and sometimes-required roles. For example, requirements always need pm, ux-designer, pe-designer, and sde-iii, while legal-expert is triggered conditionally, such as when customer data privacy is involved.

What happens when a COS request is ambiguous?▼

The intake process prompts scope clarification questions before proceeding, such as asking whether a Slack integration is outbound, inbound, or bidirectional. User confirmation of the generated plan is required before specialist orchestration begins.

When should I not use the COS intake skill?▼

Do not use it for coding or implementation tasks, since it is designed for business, product, and strategic work only. It is an intake and planning layer, so it does not produce the final deliverable itself; specialist agents handle execution after the plan is approved.