Best use case
generate-tasks is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Convert PRD to structured task list with automatic linking
Teams using generate-tasks 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/generate-tasks/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How generate-tasks Compares
| Feature / Agent | generate-tasks | 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?
Convert PRD to structured task list with automatic linking
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
# generate-tasks **Category**: Task Management ## Usage ```bash generate-tasks <prd-file> [--output-dir <directory>] ``` ## Arguments - `<prd-file>`: Required - Path to the PRD file to convert - `--output-dir`: Optional - Directory for task file (default: ./tasks/) ## Execution Instructions for Claude Code When this command is run, Claude Code should: 1. Read the PRD file and extract metadata 2. Analyze PRD content to generate a comprehensive task list 3. Create task file with proper naming convention: - For `*-prd.md`: create `*-prd-tasks.md` - For `*-frd.md`: create `*-frd-tasks.md` - For `*-simple-frd.md`: create `*-simple-frd-tasks.md` 4. Save task file in the specified output directory (create if needed) 5. Update the PRD with a reference to the generated task file: - Add or update the "Implementation Tracking" section - Include task file path and generation date 6. Follow any additional process in the source documentation ## Task File Format Generated task file should include: ```markdown # [PRD Title] Implementation Tasks Source PRD: [relative path to PRD] Generated: [date] Total Tasks: [count] Completed: 0 ## Tasks - [ ] 1.0 Setup and Configuration - [ ] 1.1 Review relevant documentation - [ ] 1.2 Set up development environment - [ ] 2.0 Core Implementation - [ ] 2.1 [Specific task based on PRD] ... ``` ## PRD Update Add to PRD under "Implementation Tracking" section: ```markdown ## Implementation Tracking Task List: ./tasks/[filename]-tasks.md Generated: 2025-01-06 Status: See task file for current progress ``` ## Source Content Location The full process documentation can be found at: `claude_settings/python/shared/processes/task-generation.md` Claude Code should read this file and follow the documented process exactly. ## Example ```bash # Generate tasks in default location generate-tasks user-auth-frd.md # Generate tasks in specific directory generate-tasks inventory-prd.md --output-dir ../tasks/ # Generate from PRD in another directory generate-tasks ./drafts/feature-prd.md ``` ## Implementation Tips for Claude Code 1. **Smart Task Generation**: Analyze PRD sections to create relevant tasks 2. **Task Grouping**: Organize tasks by implementation phases 3. **Documentation First**: Always include doc review as first subtask 4. **Path Management**: Use relative paths for portability 5. **Metadata Preservation**: Extract PRD title and key info for task file header
Related Skills
zod
Zod schema validation patterns and type inference. Auto-loads when validating schemas, parsing data, validating forms, checking types at runtime, or using z.object/z.string/z.infer in TypeScript.
typescript-import-style
Merge-friendly import formatting (one-per-line, alphabetical). Auto-loads when writing TypeScript/JavaScript imports to minimize merge conflicts in parallel development. Enforces consistent grouping and sorting.
setup-mcp-auth
Configure authentication for an existing FastMCP server
fastmcp
FastMCP TypeScript framework patterns for MCP servers. Auto-loads when building MCP servers, creating tools/resources/prompts, implementing authentication, configuring transports, or working with FastMCP in TypeScript.
add-mcp-tool
Add a new tool to an existing FastMCP server with guided configuration
add-mcp-resource
Add a new resource or resource template to an existing FastMCP server
plan-with-team
Validate plan file ownership
privacy-compliance
GDPR, CCPA, and privacy compliance guidance for data protection. Use when handling personal data, implementing consent management, or ensuring regulatory compliance across jurisdictions.
oauth
OAuth 2.0 and OpenID Connect implementation patterns. Use when implementing authentication, authorization flows, or integrating with OAuth providers like Google, GitHub, or custom identity providers.
mcp-security
Use when securing MCP servers, preventing prompt injection, implementing authorization, validating user input, or building secure multi-agent pipelines. Provides 5-layer defense architecture patterns.
rag-cag-security
Security patterns for RAG and CAG systems with multi-tenant isolation. Use when building retrieval-augmented or cache-augmented generation systems that require tenant isolation, access control, and secure data handling.
chunking-strategies
Document chunking strategies for RAG systems. Use when implementing document processing pipelines to determine optimal chunking approaches based on document type and retrieval requirements.