workflow-project-intake

Clarify vague project ideas into structured requirements and route to workflows.

1|Updated Feb 25, 2026

Search Tags:#project planning #idea validation #artifact generation #workflow routing #requirements clarification #project intake

Ready to run

npx skills add https://github.com/mshaheerz/hive-mind --skill workflow-project-intake-mshaheerz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-project-intake
Source: https://github.com/mshaheerz/hive-mind/tree/main/agent-skills/workflow-project-intake
Command: npx skills add https://github.com/mshaheerz/hive-mind --skill workflow-project-intake-mshaheerz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users clarify vague project ideas or requirements into a structured, executable plan, ensuring the right workflow is chosen for implementation.

Core Features & Use Cases

Requirement Clarification: Guides users through a series of questions to define project goals, success criteria, and key technical switches (database, billing, auth, deployment).
Intelligent Routing: Determines the most appropriate downstream workflow (e.g., workflow-ship-faster) based on clarified requirements.
Artifact Persistence: Saves clarified requirements and context into proposal.md and context.json for traceability and downstream use.
Use Case: A user has a general idea for a new web app. This Skill will help them define what the app should do, how to measure success, and whether it needs a database or authentication, before handing it off to a development workflow.

Quick Start

Use the workflow-project-intake skill to clarify requirements for a new project idea.

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 executable requirements?▼

To clarify vague project ideas into executable requirements, use a structured questioning protocol to define goals, success criteria, non-goals, and technical switches like database and authentication needs. This process transforms abstract concepts into a structured plan.

What is the best way to document project intake and technical requirements?▼

The best way to document project intake is to persist clarified requirements and context into structured artifacts like proposal.md and context.json. This ensures traceability and provides downstream workflows with necessary implementation inputs.

How do I route a validated project idea to an implementation workflow?▼

Route a validated project idea to an implementation workflow by evaluating clarified requirements and technical switches. The intake process determines the most appropriate downstream workflow, such as workflow-ship-faster, based on your defined project parameters.

What technical requirements should I define during project intake?▼

During project intake, define key technical requirements including database needs, billing integration, authentication methods, and deployment configurations. Also establish clear success criteria and non-goals to bound the project scope effectively.

Can I use this project intake process for a new web app idea?▼

Yes, you can use this project intake process for a new web app idea. It guides you to define what the app should do, how to measure success, and whether it needs a database or authentication before handing it off to a development workflow.

Why define non-goals during the project planning phase?▼

Define non-goals during project planning to prevent scope creep and ensure development workflows focus only on executable inputs. Establishing boundaries helps clarify the exact deliverables and technical switches required for successful implementation.