project-intake

Name: project-intake
Availability: InStock
Author: maosanhioro

Clarify project goals, constraints, and unknowns into a structured intake checklist.

Updated Jan 26, 2026

Search Tags:#scoping #checklist #requirements #handoff #project-planning #intake

Ready to run

npx skills add https://github.com/maosanhioro/dotfiles --skill project-intake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-intake
Source: https://github.com/maosanhioro/dotfiles/tree/main/copilot/skills-templates/project-intake
Command: npx skills add https://github.com/maosanhioro/dotfiles --skill project-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly gathers and clarifies goals, constraints, unknowns, and acceptance criteria so teams can move from vague requests to actionable work without prolonged back-and-forth.

Core Features & Use Cases

Structured Intake Checklist: Walks through Goal, Non-Goals, Facts, Unknowns, and Validation Plan to ensure consistent coverage.
Scope & Handoff Clarity: Reduces ambiguity for engineering, design, and cross-agent handoffs by documenting assumptions and verification steps.
Use Case: When a stakeholder submits a feature request with incomplete details, use this checklist to align the team, identify blockers, and create a validation path before implementation.

Quick Start

Use this checklist to produce a Goal, Non-Goals, Facts, Unknowns, and a Validation Plan for the new feature request so the team can estimate and start work.

Frequently Asked Questions about project-intake

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

FAQPage Schema

How do I clarify project scope for a vague feature request?▼

Clarify project scope for a vague feature request by walking through a structured intake checklist to document Goals, Non-Goals, Facts, and Unknowns. This ensures consistent coverage and reduces ambiguity before implementation begins.

What is the best way to handle cross-agent handoffs for incoming work?▼

Handle cross-agent handoffs by generating a concise intake document that captures assumptions, constraints, and a validation plan. This reduces ambiguity and provides a clear scoping path for downstream engineering or design tasks.

How do I align stakeholder goals and identify project unknowns?▼

Align stakeholder goals and identify project unknowns by rapidly collecting consensus during initial intake meetings using a structured checklist. This outputs a clear validation plan to support scoping and estimation.

Can I use a checklist to estimate and start work on incomplete change requests?▼

Use a checklist to estimate and start work on incomplete change requests by producing a validation plan alongside documented Facts and Unknowns. This allows the team to identify blockers and create a verification path before implementation.

When do I need a project intake checklist for requirements gathering?▼

You need a project intake checklist for requirements gathering when a stakeholder submits a request with incomplete details or when facing ambiguous change requests. It helps rapidly collect consensus and necessary assumptions to move from vague requests to actionable work.