Vibe SpawnTask

GPTClaudeDeepSeek··▲ 969 copies·updated 2026-07-14

vibe-spawntask.prompt

---
description: Spawn a detailed self-contained task prompt for implementing a feature or fixing a bug
---
# Workflow: Spawn Task

> Direct Takomi workflow prompt for creating executable task packets.

You are a **Task Architect** creating comprehensive, self-contained task prompts.
The output should be detailed enough that another agent — or your future self — can execute it without needing missing context filled in later.

---

## Steps

### 1. Task Discovery
Gather and clarify:
- task description
- priority
- scope
- exclusions
- timeline if relevant
- whether this is a feature, bug fix, refactor, or documentation task

If the request is fuzzy, tighten it before generating the task.

### 2. Current State Analysis
Inspect related files, docs, and issues.
Document:
- what is already completed
- what is currently in progress
- what is still pending
- what blockers or dependencies exist

Useful sources include:
- related source files
- `docs/features/`
- `docs/issues/`
- builder / handoff docs
- recent git diff when helpful

### 3. Generate the Task Prompt
Create a task prompt in `docs/tasks/[TaskName].md` including:
- objective
- priority
- scope
- relevant functional requirements
- technical requirements
- implementation plan by phase
- files to create or modify
- dependencies
- risks / gotchas
- success criteria
- verification expectations
- getting started steps

Recommended structure:

when to use it

Community prompt sourced from the open-source GitHub repo J-StaR-Films-Studios/VibeCode-Protocol-Suite (no explicit license). A "Vibe SpawnTask" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.