repository·main·Indexed 27 days ago
https://github.com/snarktank/ai-dev-tasksA structured markdown-based workflow for building complex features using AI-powered IDEs and CLIs. It provides a systematic process for moving from monolithic prompts to iterative implementation via PRD creation and task decomposition, utilizing specific prompt files like create-prd.md and generate-tasks.md to guide AI assistants in drafting blueprints and granular, step-by-step implementation plans.
To use the structured prompts in your development workflow, clone the repository to a location accessible by your AI coding assistant (e.g., Amp, Claude Code, Windsurf).
git clone https://github.com/snarktank/ai-dev-tasks.gitTo maintain control and ensure quality, do not ask the AI to complete the entire list at once. Instead, instruct it to work through the generated task list one sub-task at a time (e.g., task 1.1). This allows you to review and approve changes at each small step.
Please start on task 1.1 from the generated task list.Use the create-prd.md file to guide your AI assistant in drafting a blueprint for your new feature. This clarifies the scope, audience, and purpose before implementation begins.
Use @create-prd.md
Here's the feature I want to build: [Describe your feature in detail]
Reference these files to help you: [Optional: @file1.py @file2.ts]To implement a new feature using this workflow, provide your feature request, task description, or existing documentation to the AI assistant. The assistant will follow a two-phase process to create a structured implementation guide.
0.0 Create feature branch unless instructed otherwise.Go, the AI breaks each parent task into actionable sub-tasks, identifies relevant files, and generates the final Markdown file./tasks/tasks-[feature-name].md (e.g., tasks-user-profile-editing.md)To initiate a new feature development workflow, provide an AI assistant with a brief description of the desired functionality. The AI will follow a specific process to ensure the resulting PRD is actionable for a junior developer.
1A, 2C)./tasks directory with the naming convention prd-[feature-name].md.Once you have a PRD (e.g., MyFeature-PRD.md), use the generate-tasks.md file to instruct the AI to break the requirements down into a granular, step-by-step implementation plan.
Now take @MyFeature-PRD.md and create tasks using @generate-tasks.mdEvery generated PRD must follow this specific Markdown structure to ensure clarity for developers:
The generated task list follows a specific Markdown structure designed for developers to track progress. It includes a section for relevant files, implementation notes, and a hierarchical task list.
A list of files that need to be created or modified, including their test counterparts.
## Relevant Files
- `path/to/potential/file1.ts` - Brief description of why this file is relevant.
- `path/to/file1.test.ts` - Unit tests for `file1.ts`.General implementation guidance, such as testing patterns or command usage.
### Notes
- Unit tests should typically be placed alongside the code files they are testing.
- Use `npx jest [optional/path/to/test/file]` to run tests.A nested list of parent tasks and sub-tasks using Markdown checkboxes.
## Instructions for Completing Tasks
**IMPORTANT:** As you complete each task, you must check it off in this markdown file by changing `- [ ]` to `- [x]`.
## Tasks
- [ ] 0.0 Create feature branch
- [ ] 0.1 Create and checkout a new branch for this feature (e.g., `git checkout -b feature/[feature-name]`)
- [ ] 1.0 Parent Task Title
- [ ] 1.1 [Sub-task description 1.1]
- [ ] 2.0 Parent Task Title## Relevant Files
- `path/to/potential/file1.ts` - Brief description of why this file is relevant (e.g., Contains the main component for this feature).
- `path/to/file1.test.ts` - Unit tests for `file1.ts`.
- `path/to/another/file.tsx` - Brief description (e.g., API route handler for data submission).
- `path/to/another/file.test.tsx` - Unit tests for `another/file.tsx`.
- `lib/utils/helpers.ts` - Brief description (e.g., Utility functions needed for calculations).
- `lib/utils/helpers.test.ts` - Unit tests for `helpers.ts`.
### Notes
- Unit tests should typically be placed alongside the code files they are testing (e.g., `MyComponent.tsx` and `MyComponent.test.tsx` in the same directory).
- Use `npx jest [optional/path/to/test/file]` to run tests. Running without a path executes all tests found in the Jest configuration.
## Instructions for Completing Tasks
**IMPORTANT:** As you complete each task, you must check it off in this markdown file by changing `- [ ]` to `- [x]`. This helps track progress and ensures you don't skip any steps.
Example:
- `- [ ] 1.1 Read file` → `- [x] 1.1 Read file` (after completing)
Update the file after completing each sub-task, not just after completing an entire parent task.
## Tasks
- [ ] 0.0 Create feature branch
- [ ] 0.1 Create and checkout a new branch for this feature (e.g., `git checkout -b feature/[feature-name]`)
- [ ] 1.0 Parent Task Title
- [ ] 1.1 [Sub-task description 1.1]
- [ ] 1.2 [Sub-task description 1.2]
- [ ] 2.0 Parent Task Title
- [ ] 2.1 [Sub-task description 2.1]
- [ ] 3.0 Parent Task Title (may not require sub-tasks if purely structural or configuration)The repository contains two primary prompt files used to drive the workflow:
create-prd.md: Guides the AI in generating a Product Requirement Document.generate-tasks.md: Converts a PRD markdown file into a detailed, step-by-step implementation task list.Generated Product Requirements Documents must adhere to the following output specifications:
.md)/tasks/prd-[feature-name].md