task-generator
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
Best use case
task-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
Teams using task-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/task-generator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How task-generator Compares
| Feature / Agent | task-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Task Generator Generate detailed, step-by-step task lists from specs, plans, or requirements. ## Workflow (2-Phase Process) ### Phase 1: Generate Parent Tasks 1. Analyze the spec/plan content for functional requirements and implementation scope 2. Create the task file at `/tasks/tasks-[feature-name].md` 3. Generate 5-7 high-level parent tasks: - **Always start with task 0.0**: "Create feature branch" (unless user explicitly opts out) - Use your judgment for the number of additional tasks 4. Present parent tasks to user in the output format (without sub-tasks) 5. Tell user: "I have generated the high-level tasks. Ready to generate sub-tasks? Reply **Go** to proceed." ### Phase 2: Generate Sub-Tasks 1. Wait for user to reply "Go" 2. Break down each parent task into smaller, actionable sub-tasks 3. Identify relevant files to create/modify (include test files) 4. Update the task file with complete structure ## Output Format Save to `/tasks/tasks-[feature-name].md`: ```markdown ## Relevant Files - `path/to/file.ts` - Brief description of why this file is relevant - `path/to/file.test.ts` - Unit tests for file.ts - `path/to/component.tsx` - Component description - `path/to/component.test.tsx` - Unit tests for component.tsx ### Notes - Unit tests should be placed alongside the code files they test - Use `npx jest [optional/path/to/test/file]` to run tests ## Instructions for Completing Tasks **IMPORTANT:** As you complete each task, check it off by changing `- [ ]` to `- [x]`. Update after completing each sub-task. ## Tasks - [ ] 0.0 Create feature branch - [ ] 0.1 Create and checkout new branch (`git checkout -b feature/[feature-name]`) - [ ] 1.0 [Parent Task Title] - [ ] 1.1 [Sub-task description] - [ ] 1.2 [Sub-task description] - [ ] 2.0 [Parent Task Title] - [ ] 2.1 [Sub-task description] ``` ## Guidelines - **Target audience**: Junior developer who will implement the feature - **Task style**: Use imperative verbs (Create, Add, Implement, Update) - **Feature name**: Derive from spec title/topic in kebab-case - **File identification**: Include both source and test files - **Sub-task granularity**: Each sub-task should be completable in one focused session
Related Skills
Wheels Migration Generator
Generate database-agnostic Wheels migrations for creating tables, altering schemas, and managing database changes. Use when creating or modifying database schema, adding tables, columns, indexes, or foreign keys. Prevents database-specific SQL and ensures cross-database compatibility.
smart-contract-generator
Generates Solidity smart contracts with security best practices (ERC-20, ERC-721, ERC-1155, custom). Use when user asks to "create smart contract", "solidity contract", "erc20 token", "nft contract", or "web3 contract".
run-nx-generator
Run Nx generators with prioritization for workspace-plugin generators. Use this when generating code, scaffolding new features, or automating repetitive tasks in the monorepo.
k8s-manifest-generator
Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
card-news-generator-v2
Create 600x600 Instagram-style card news series automatically with optional background images. User provides topic, colors, and optional images - Claude generates content and creates multiple cards with proper text wrapping.
zapier-workflows
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
writing-skills
Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dependencies, and rust-documentation skills.
writing-plans
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
workflow-management
Create, debug, or modify QStash workflows for data updates and social media posting in the API service. Use when adding new automated jobs, fixing workflow errors, or updating scheduling logic.
workflow-interactive-dev
用于开发 FastGPT 工作流中的交互响应。详细说明了交互节点的架构、开发流程和需要修改的文件。