roster-intake

Convert raw task inputs into validated briefs for Roster pipeline workflows.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/mathiasbourgoin/roster --skill roster-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roster-intake
Source: https://github.com/mathiasbourgoin/roster/tree/main/.opencode/skills/roster-intake
Command: npx skills add https://github.com/mathiasbourgoin/roster --skill roster-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vague or incomplete task descriptions lead to misaligned execution, wasted effort, and rework in multi-agent development pipelines. This skill eliminates that risk by transforming raw task inputs into a clear, comprehensive, and human-validated brief that serves as the single source of truth for all downstream pipeline phases.

Core Features & Use Cases

  • Context-Aware Brief Generation: Ingests existing project context (knowledge base files, AGENTS.md, README, optional prior research) to build a complete understanding of the task before asking any questions.
  • Targeted Clarification: Only asks questions for gaps that cannot be inferred from available resources, avoiding unnecessary back-and-forth with the user.
  • Structured Output & Validation: Produces a standardized brief covering task goal, scope, relevant files, architecture notes, quality gates, and open questions, then requires explicit human validation before allowing the pipeline to proceed.
  • Use Case: For a team using the Roster pipeline, assigning a "add user authentication" task will generate a validated brief outlining in-scope components, relevant auth-related files, exact test commands, and open questions about OAuth provider support, so the implementation phase has zero ambiguity.

Quick Start

Invoke the roster-intake skill with your raw task description to generate a validated, unambiguous brief that the rest of the Roster pipeline will use as its single source of truth.

Frequently Asked Questions about roster-intake

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

FAQPage Schema
How do I create validated task briefs for multi-agent development pipelines?

Task brief generation eliminates ambiguity by transforming raw task inputs into structured, validated briefs covering scope, relevant files, and quality gates. It ingests project context like knowledge base files and AGENTS.md, asks targeted clarification questions, and requires mandatory human validation before pipeline execution proceeds.

How do I prevent scope misalignment in multi-agent software development pipelines?

Prevent scope misalignment by translating raw task inputs into structured, human-validated briefs that serve as a single source of truth. Covering task scope, relevant files, architecture notes, quality gates, and open questions ensures downstream planning and implementation phases have zero ambiguity.

How do I generate a pipeline brief from existing project context and documentation?

Generate a pipeline brief by ingesting existing project context such as knowledge base files, AGENTS.md, README, and prior research. The system builds a complete understanding before asking targeted clarification questions only for gaps that cannot be inferred from available resources.

Can I use roster-intake for agent orchestration without writing detailed task specifications?

Yes, you can use roster-intake for agent orchestration without detailed specifications. It ingests raw task descriptions and existing project context to automatically generate comprehensive briefs, asking only for clarification on gaps and requiring explicit human validation before execution proceeds.

What is the best way to define task scope and quality gates for multi-agent pipelines?

The best way to define task scope and quality gates is producing a standardized, human-validated brief covering in-scope components, relevant files, exact test commands, and open questions. This structured approach ensures all downstream pipeline phases operate with zero ambiguity.