spawn-task
Spawn Task Skill
Create detailed task prompts that another agent (or future self) can execute without additional context.
When to Use
- Breaking down complex features
- Creating implementation specs
- When user says "spawn a task for..."
- Planning multi-phase work
Task Discovery
Gather from user:
- Task Description: What needs to be done?
- Priority: High / Medium / Low
- Scope: What's included/excluded?
- Timeline: Expected completion (optional)
Current State Analysis
# Check related files
find src -name "*relevant*" -type f
# Check documentation
ls docs/features/
# Check GitHub issues
gh issue list --search "[related term]"
Task Prompt Template
Create docs/tasks/[TaskName].md:
# 🎯 Task: [Task Name]
**Objective:** [Clear, measurable goal]
**Priority:** [High/Medium/Low]
**Scope:** [What's included/excluded]
---
## 📋 Requirements
### Functional Requirements
- **[REQ-001]** [Requirement with acceptance criteria]
### Technical Requirements
- **[TECH-001]** [Technical specification]
---
## 🏗️ Implementation Plan
### Phase 1: Setup
- [ ] [Setup task]
### Phase 2: Core Implementation
- [ ] [Core task]
### Phase 3: Enhancement
- [ ] [Enhancement task]
### Phase 4: Testing & Documentation
- [ ] [Testing task]
---
## 📁 Files to Create/Modify
| File | Action | Purpose |
|------|--------|---------|
| `src/features/[Feature]/...` | Create | [Purpose] |
---
## ✅ Success Criteria
### Code Quality
- [ ] TypeScript compliant (no `any`)
- [ ] Passes ESLint
- [ ] Unit tests with >80% coverage
### Performance
- [ ] Bundle size increase < 5KB
- [ ] Load time < 1.5s
### Functionality
- [ ] All requirements implemented
- [ ] Mobile responsive
---
## 🔗 Dependencies
**Depends on:** [Other components]
**Used by:** [Components that use this]
---
## 🚀 Getting Started
1. Read this task prompt completely
2. Review related files
3. Begin with Phase 1
4. Provide progress updates after each phase
Options After Spawning
- A) Start implementing now
- B) Create GitHub Issue to track
- C) Save task for later
Task Categories
- 🆕 Feature: New functionality
- 🐛 Bug Fix: Fixing broken behavior
- ♻️ Refactor: Improving existing code
- 📚 Documentation: Writing docs
Priority Guidelines
- High: Blocking other work, user-facing bugs
- Medium: Important features, non-blocking issues
- Low: Nice-to-haves, minor improvements
More from jstarfilms/vibecode-protocol-suite
google-trends
Automated Google Trends research via Node.js CLI. Search YouTube, Web, Images, News for rising/breakout queries. Use for Phase 1 Strategy research or any topic validation.
121youtube-pipeline
Complete YouTube video production pipeline from ideation to distribution. Covers Strategy (Phase 1), Packaging (Phase 2), Scripting (Phase 3), Shorts (Phase 3.5), Production (Phase 4), and Repurposing (Phase 5).
84ui-ux-pro-max
Comprehensive design guide for web and mobile applications. Contains 50+ styles, 97 color palettes, 57 font pairings, 99 UX guidelines, and 25 chart types. Use when the user requests UI/UX work (design, build, create, implement, review, fix, improve).
36security-audit
Perform a meticulous deep code audit covering Security, Logic, Completeness, and Quality. Includes vibe-coding-specific guardrails for supply chain attacks, auth, rate limiting, and RLS.
33nextjs-standards
Comprehensive coding standards, verification protocols, and templates for Next.js App Router projects. Auto-loads on Next.js detection.
33stitch
|
30