workflow-project-intake

Clarify project requirements and route to the appropriate workflow.

339|58|Updated Jan 10, 2026

Search Tags:#workflow #documentation #routing #requirements #brainstorm #artifact #intake

Ready to run

npx skills add https://github.com/Heyvhuang/ship-faster --skill workflow-project-intake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-project-intake
Source: https://github.com/Heyvhuang/ship-faster/tree/main/skills/workflow-project-intake
Command: npx skills add https://github.com/Heyvhuang/ship-faster --skill workflow-project-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill clarifies requirements and routes to the right workflow, turning vague ideas into actionable intake and routing decisions that keep work moving.

Core Features & Use Cases

Intake & Brainstorming: Helps users articulate goals, constraints, success criteria, and next steps.
Artifact Persistence: Persists goals/context artifacts to enable replayable execution and audit trails.
Routing to Workflows: Dispatches to the appropriate downstream skill (default to workflow-ship-faster) based on input type or trigger.
Triggers: Project kickoff, requirements clarification, brainstorm, ideas, discovery, and intake.

Quick Start

Begin by providing either a project idea or a repository path. The skill will ask one focused question at a time to fill in missing details, persist the gathered context, and route to the default workflow unless you specify a different target skill.

Frequently Asked Questions about workflow-project-intake

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

FAQPage Schema

How do I clarify vague project ideas into actionable requirements?▼

Requirements clarification uses structured intake to turn vague ideas into actionable plans. It asks one focused question at a time to identify goals, constraints, and success criteria, persisting the gathered context as an artifact for replayable execution.

What is the best way to route requirements to a downstream workflow?▼

The best way to route requirements is to use an intake skill that evaluates your input type or trigger and dispatches the context to a target workflow. It defaults to workflow-ship-faster but allows specifying a different downstream skill when ready.

How do I persist project context for replayable execution and audit trails?▼

Persist project context for replayable execution by saving goals and artifacts during the intake and brainstorming phase. This creates a persistent record that supports audit trails and allows downstream workflows to access the original requirements.

Can I use a single-question intake process for project kickoff and discovery?▼

Yes, you can use a single-question intake process for project kickoff and discovery. It enforces a structured workflow by asking one focused question at a time to fill in missing details, ensuring requirements are captured accurately before routing.

Do I need a prototype or repository path to start brainstorming project requirements?▼

You do not need a complete prototype to start brainstorming requirements; providing either a project idea or a repository path is sufficient. The intake process will then guide you through checkpointed write plans to clarify any missing details.

Why does my requirements intake workflow need checkpointed write plans?▼

Requirements intake workflows need checkpointed write plans to enforce structured progress and prevent context loss. By checkpointing gathered information, the workflow ensures goals and constraints are safely persisted before routing to downstream execution.